You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: gui-tool-tutorials/github-windows-vs2017-tutorial.md
+19-19Lines changed: 19 additions & 19 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ If you don't have Visual Studio 2017 on your machine, [install it](https://www.v
16
16
17
17
## Fork this repository
18
18
19
-
<imgalign="right"width="300"src="https://firstcontributions.github.io/assets/Readme/fork.png"alt="fork this repository" />
19
+
<imgalign="right"width="300"src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png"alt="fork this repository" />
20
20
21
21
Fork this repository by clicking on the fork button on the top of this page. This will create of copy of this repository in your GitHub account.
22
22
@@ -26,102 +26,102 @@ Most top-level GitHub repos (i.e. ones not forked from any other repo) have a sm
26
26
27
27
## Clone your repository
28
28
29
-
<imgalign="right"width="300"src="https://firstcontributions.github.io/assets/Readme/clone.png"alt="clone this repository" />
29
+
<imgalign="right"width="300"src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png"alt="clone this repository" />
30
30
31
31
The next step is to clone your repo down to your machine so you can begin making changes. Visual Studio needs the URL of your repo, so click the "clone" button and then click the "copy to clipboard" icon.
32
32
33
33
**CAREFUL:** One mistake that new contributors often make is to clone the repo you forked *from* rather than cloning your repo. Check your browser's address bar and make sure you are cloning your repo.
34
34
35
35
It is now time to jump in to Visual Studio 2017! You will be working in the Team Explorer tab for most of this tutorial. If it is not open by default, click `View > Team Explorer` to open it.
Team Explorer has many views and there are navigation buttons located at the top to help you find the different areas. To clone a repo, you need to be on the Connect view, which should be the default. If you do not see the 'clone' button, click the green plug at the top.
40
40
41
41
Click the `Clone` option under **Local Git Repositories** and paste the URL to your repo in the text box. This should be the URL you copied to your clipboard from GitHub previously.
When the process is complete you will be moved over to the Solution Explorer tab where you can see the contents of your repo. Yours will look different than the screenshot below because things change!
You should see the **first-contributions** repo and the default branch, which is called `master`. Right-click on `master` and choose `New Local Branch From...`.
<imgsrc="../assets/vs2017-07-branch4.png"alt="See new branch" />
69
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png"alt="See new branch" />
70
70
71
71
## Make necessary changes
72
72
73
73
Open `Contributors.md` and add your name to the end of the list. This file contains GFM (GitHub Flavored Markdown) which is a proprietary flavor of the <ahref="https://en.wikipedia.org/wiki/Markdown">markdown</a> syntax.
74
74
75
75
Copy one of the other contributors' lines and modify it with your name to make sure you get the syntax right - it can be picky.
76
76
77
-
<imgsrc="../assets/vs2017-08-change1.png"alt="Add your name" />
77
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png"alt="Add your name" />
78
78
79
79
## Commit & Push changes to GitHub
80
80
81
81
Switch back to Team Explorer and navigate to the Changes view.
Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits.
86
86
87
-
<imgsrc="../assets/vs2017-10-commit2.png"alt="Git user information" />
87
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png"alt="Git user information" />
88
88
89
89
**NOTE:** Visual Studio uses a hidden folder called `.vs` to store your personal settings and preferences. The contents of this folder **should not be saved in Git**.
90
90
If it has not been ignored already, you may need to tell Git to ignore this folder so it does not send it up to the repo.
91
91
92
92
This folder has already been ignored in this repo, so you should not have to perform this step...it is just here for your reference for future projects.
93
93
94
-
<imgsrc="../assets/vs2017-11-commit3.png"alt="Ignore vs folder" />
94
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png"alt="Ignore vs folder" />
95
95
96
96
Now you should see a list of changed files and a textbox to type a commit comment. Comments should be in brief but thorough. There is nothing worse than reading through commit comments and seeing this: `"I updated some stuff"`. Take a few seconds to outline your commit. Your team will thank you later, and you might even thank yourself!
97
97
98
98
Click `Commit All and Push` to perform a local commit and push your changes back up to your repo, all in one step.
99
99
100
100
**NOTE:** Commit can be performed separately from Push. We do both here for convenience. Commit logs your changes locally but they will not be reflected in your GitHub repo until you Push.
101
101
102
-
<imgsrc="../assets/vs2017-12-commit4.png"alt="Commit and Push" />
102
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png"alt="Commit and Push" />
103
103
104
104
The first time you Push to GitHub, Visual Studio will ask for your GitHub credentials. They will be cached so you should not see this very often.
After the Push operation completes, open your repo in GitHub and you should see a message indicating a recently pushed branch.
109
109
110
110
You can view your changes by opening the `Branch: master` dropdown and selecting your new branch. Congratulations, you can share the branch URL with the world to show your progress!
111
111
112
-
<imgsrc="../assets/vs2017-14-commit6.png"alt="View pushed branch on GitHub" />
112
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png"alt="View pushed branch on GitHub" />
113
113
114
114
## Submit your changes for review
115
115
116
116
At this point you have completed your change but it still only resides in your repo. This step will show you how to submit a request to the administrator of the top-level repo to merge your change.
117
117
118
118
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
119
119
120
-
<imgsrc="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png"alt="create a pull request" />
120
+
<imgsrc="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png"alt="create a pull request" />
0 commit comments