mirrors/90DaysOfDevOps
1
0
Fork 0
mirror of https://github.com/MichaelCade/90DaysOfDevOps.git synced 2024-12-22 22:33:12 +07:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #442 from phamtruc-work/main

Browse Source
This commit is contained in:
Michael Cade 2023-08-29 05:55:12 +01:00 committed by GitHub
commit 397ab43be1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
2022/Days/day40.md
View File

@ -73,7 +73,7 @@ We can then drill down into the building block of GitHub, the repositories. Here
As the repository is so important to GitHub let me choose a pretty busy one of late and run through some of the core functionality that we can use here on top of everything I am already using when it comes to editing our "code" in git on my local system.
First of all, from the previous window, I have selected the 90DaysOfDevOps repository and we get to see this view. You can see from this view we have a lot of information, we have our main code structure in the middle showing our files and folders that are stored in our repository. We have our readme. mdbeing displayed down at the bottom. Over to the right of the page, we have an about section where the repository has a description and purpose. Then we have a lot of information underneath this showing how many people have starred in the project, forked, and watched.
First of all, from the previous window, I have selected the 90DaysOfDevOps repository and we get to see this view. You can see from this view we have a lot of information, we have our main code structure in the middle showing our files and folders that are stored in our repository. We have our readme.md being displayed down at the bottom. Over to the right of the page, we have an about section where the repository has a description and purpose. Then we have a lot of information underneath this showing how many people have starred in the project, forked, and watched.
![](Images/Day40_Git8.png)
@ -179,7 +179,7 @@ Let's now make some changes, I want to make a change to all those links and repl
![](Images/Day40_Git27.png)
Now if we check back on GitHub and we find our readme.mdin that repository, you should be able to see a few changes that I made to the file.
Now if we check back on GitHub and we find our readme.md in that repository, you should be able to see a few changes that I made to the file.
![](Images/Day40_Git28.png)

8
2022/Days/day41.md
View File

@ -16,7 +16,7 @@ When we went through the GitHub fundamentals we went through the process of fork
## Fork a Project
The first thing we have to do is find a project we can contribute to. I have recently been presenting on the [Kanister Project](https://github.com/kanisterio/kanister) and I would like to share my presentations that are now on YouTube to the main readme.mdfile in the project.
The first thing we have to do is find a project we can contribute to. I have recently been presenting on the [Kanister Project](https://github.com/kanisterio/kanister) and I would like to share my presentations that are now on YouTube to the main readme.md file in the project.
First of all, we need to fork the project. Let's run through that process. I am going to navigate to the link shared above and fork the repository.
@ -26,7 +26,7 @@ We now have our copy of the whole repository.
![](Images/Day41_Git2.png)
For reference on the Readme.mdfile the original Presentations listed are just these two so we need to fix this with our process.
For reference on the readme.md file the original Presentations listed are just these two so we need to fix this with our process.
![](Images/Day41_Git3.png)
@ -42,7 +42,7 @@ We have our project local so we can open VSCode or an IDE or text editor of your
![](Images/Day41_Git5.png)
The readme.mdfile is written in markdown language and because I am modifying someone else's project I am going to follow the existing project formatting to add our content.
The readme.md file is written in markdown language and because I am modifying someone else's project I am going to follow the existing project formatting to add our content.
![](Images/Day41_Git6.png)
@ -76,7 +76,7 @@ Next, we hit that contribute button highlighted above. We see the option to "Ope
## Open a pull request
There is quite a bit going on in this next image, top left you can now see we are in the original or the master repository. then you can see what we are comparing and that is the original master and our forked repository. We then have a create pull request button which we will come back to shortly. We have our single commit but if this was more changes you might have multiple commits here. then we have the changes we have made in the readme.mdfile.
There is quite a bit going on in this next image, top left you can now see we are in the original or the master repository. then you can see what we are comparing and that is the original master and our forked repository. We then have a create pull request button which we will come back to shortly. We have our single commit but if this was more changes you might have multiple commits here. then we have the changes we have made in the readme.md file.
![](Images/Day41_Git12.png)