Skip to content

Commit 2186e7a

Browse files
authored
Update github-windows-vs2017-tutorial.md
1 parent 4dd2710 commit 2186e7a

File tree

1 file changed

+19
-19
lines changed

1 file changed

+19
-19
lines changed

gui-tool-tutorials/github-windows-vs2017-tutorial.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ If you don't have Visual Studio 2017 on your machine, [install it](https://www.v
1616

1717
## Fork this repository
1818

19-
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/fork.png" alt="fork this repository" />
19+
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/fork.png" alt="fork this repository" />
2020

2121
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.
2222

@@ -26,102 +26,102 @@ Most top-level GitHub repos (i.e. ones not forked from any other repo) have a sm
2626

2727
## Clone your repository
2828

29-
<img align="right" width="300" src="https://firstcontributions.github.io/assets/Readme/clone.png" alt="clone this repository" />
29+
<img align="right" width="300" src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/clone.png" alt="clone this repository" />
3030

3131
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.
3232

3333
**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.
3434

3535
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.
3636

37-
<img src="../assets/vs2017-01-clone1.png" alt="Team Explorer" />
37+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-01-clone1.png" alt="Team Explorer" />
3838

3939
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.
4040

4141
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.
4242

4343
Click the `Clone` button to initiate the process.
4444

45-
<img src="../assets/vs2017-02-clone2.png" alt="Clone repo" />
45+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-02-clone2.png" alt="Clone repo" />
4646

4747
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!
4848

49-
<img src="../assets/vs2017-03-clone3.png" alt="Solution Explorer" />
49+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-03-clone3.png" alt="Solution Explorer" />
5050

5151
## Create a branch
5252

5353
Click back to the Team Explorer tab and use the main navigation dropdown to open the Branches view.
5454

55-
<img src="../assets/vs2017-04-branch1.png" alt="Branches view" />
55+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-04-branch1.png" alt="Branches view" />
5656

5757
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...`.
5858

59-
<img src="../assets/vs2017-05-branch2.png" alt="New branch" />
59+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-05-branch2.png" alt="New branch" />
6060

6161
Give your branch a name like `add-<your_name_here>`, for example: `add-alonzo-church`.
6262

6363
Leave the `Checkout branch` box checked and click the `Create Branch` button.
6464

65-
<img src="../assets/vs2017-06-branch3.png" alt="Create branch" />
65+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-06-branch3.png" alt="Create branch" />
6666

6767
You should see your new branch in the list.
6868

69-
<img src="../assets/vs2017-07-branch4.png" alt="See new branch" />
69+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-07-branch4.png" alt="See new branch" />
7070

7171
## Make necessary changes
7272

7373
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 <a href="https://en.wikipedia.org/wiki/Markdown">markdown</a> syntax.
7474

7575
Copy one of the other contributors&apos; lines and modify it with your name to make sure you get the syntax right - it can be picky.
7676

77-
<img src="../assets/vs2017-08-change1.png" alt="Add your name" />
77+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-08-change1.png" alt="Add your name" />
7878

7979
## Commit & Push changes to GitHub
8080

8181
Switch back to Team Explorer and navigate to the Changes view.
8282

83-
<img src="../assets/vs2017-09-commit1.png" alt="Changes" />
83+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-09-commit1.png" alt="Changes" />
8484

8585
Enter the information you want to post with your commit and click `Save`. Visual Studio will remember it for future commits.
8686

87-
<img src="../assets/vs2017-10-commit2.png" alt="Git user information" />
87+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-10-commit2.png" alt="Git user information" />
8888

8989
**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**.
9090
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.
9191

9292
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.
9393

94-
<img src="../assets/vs2017-11-commit3.png" alt="Ignore vs folder" />
94+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-11-commit3.png" alt="Ignore vs folder" />
9595

9696
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!
9797

9898
Click `Commit All and Push` to perform a local commit and push your changes back up to your repo, all in one step.
9999

100100
**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.
101101

102-
<img src="../assets/vs2017-12-commit4.png" alt="Commit and Push" />
102+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-12-commit4.png" alt="Commit and Push" />
103103

104104
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.
105105

106-
<img src="../assets/vs2017-13-commit5.png" alt="Login" />
106+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-13-commit5.png" alt="Login" />
107107

108108
After the Push operation completes, open your repo in GitHub and you should see a message indicating a recently pushed branch.
109109

110110
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!
111111

112-
<img src="../assets/vs2017-14-commit6.png" alt="View pushed branch on GitHub" />
112+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/vs2017-14-commit6.png" alt="View pushed branch on GitHub" />
113113

114114
## Submit your changes for review
115115

116116
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.
117117

118118
In your repo on GitHub you'll see the `Compare & pull request` button next to the new branch notification. Click on that button.
119119

120-
<img src="https://firstcontributions.github.io/assets/Readme/compare-and-pull.png" alt="create a pull request" />
120+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/compare-and-pull.png" alt="create a pull request" />
121121

122122
Now submit the pull request.
123123

124-
<img src="https://firstcontributions.github.io/assets/Readme/submit-pull-request.png" alt="submit pull request" />
124+
<img src="https://firstcontributions.github.io/assets/gui-tool-tutorials/github-windows-vs2017-tutorial/submit-pull-request.png" alt="submit pull request" />
125125

126126
Soon I'll be merging all your changes into the master branch of this project. You will get a notification email once the changes have been merged.
127127

@@ -137,4 +137,4 @@ You can join our slack team in case you need any help or have any questions. [Jo
137137
### [Additional material](../additional-material/git_workflow_scenarios/additional-material.md)
138138

139139
## Tutorials Using Other Tools
140-
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)
140+
[Back to main page](https://github.com/firstcontributions/first-contributions#tutorials-using-other-tools)

0 commit comments

Comments
 (0)