Skip to content
This repository was archived by the owner on Dec 5, 2024. It is now read-only.

Commit df1d0ba

Browse files
author
Meaghan Lewis
authored
update formatting of doc
1 parent ccf153e commit df1d0ba

File tree

1 file changed

+20
-10
lines changed

1 file changed

+20
-10
lines changed

docs/using/working-with-changes.md

Lines changed: 20 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,43 +1,53 @@
11
# Working with changes
22

3-
All changes made to a repository will show up under the **Changes** tab.
4-
53
## Commit changes to GitHub
64

5+
All changes made to a repository will show up under the **Changes** view.
6+
77
1. Select the changes to be committed. Can choose the All/None options, or select directories or files individually.
88
2. Enter a Commit summary which describes the purpose of the commit. An optional Commit description can also be entered.
99
3. Click the button `Commit to [branch name]`.
1010
<img src="images/changes-view.png" alt="Changes view"/>
1111

1212
The commit will not be shown under the **History** view. On the top bar the button `Push (1)` indicates that there is 1 commit to push.
13+
1314
<img src="images/post-commit-view.png" alt="Post commit view"/>
1415

1516
## Push changes to GitHub
1617

1718
1. Click `Push` once ready to push a commit to GitHub.
1819
<img src="images/push-view.png" alt="Push view"/>
19-
2. A dialog will appear asking `Would you like to push changes to remote 'branch name’`? Select `Push`.
20+
21+
2. A dialog will appear asking `Would you like to push changes to remote 'branch name'?` Select `Push`.
2022
<img src="images/confirm-push-changes.png" alt="Confirm push dialog"/>
23+
2124
3. Another dialog will appear when the push to GitHub is complete saying `Branch pushed`. Select `ok`.
2225
<img src="images/success-push-changes.png" alt="Branch pushed"/>
2326

2427
## Revert changes
2528

2629
1. From the **History** view, right-click on a commit in the commit list. A `Revert` option will appear.
27-
2. Click `Revert`
30+
2. Click `Revert`.
2831
<img src="images/revert.png" alt="Revert"/>
29-
3. A dialog will appear asking `1. Are you sure you want to revert the following commit: "commit message"?`. Select `Revert`.
32+
33+
3. A dialog will appear asking `Are you sure you want to revert the following commit: "commit message"?`. Select `Revert`.
3034
<img src="images/confirm-revert.png" alt="Confirm revert dialog"/>
35+
3136
4. A new commit appears titled `Revert "commit summary"` and the view indicates that there is 1 commit to push.
32-
<img src="images/revert-commit.png" alt="Revert commit"
37+
<img src="images/revert-commit.png" alt="Revert commit"/>
38+
3339
5. Follow the steps to push the reverted commit to GitHub.
3440

3541
## Pulling changes
3642

3743
1. Click the `Fetch` button to get all the latest branches and tags for the repository. The `Pull` button will then show the number of commits to pull from GitHub.
3844
2. Click `Pull`.
39-
<img src="pull-view.png" alt="Pull changes"/>
45+
<img src="images/pull-view.png" alt="Pull changes"/>
46+
4047
3. A dialog will appear asking `Would you like to pull changes from remote 'branch name'?`. Select `Pull`.
41-
<img src="confirm-pull-changes.png" alt="Confirm pull changes dialog"/>
42-
4. Another dialog appears saying `Local branch is up to date with 'branch name'`. Select `ok`.
43-
<img src="success-pull-changes.png" alt="Changes pulled"/>
48+
<img src="images/confirm-pull-changes.png" alt="Confirm pull changes dialog"/>
49+
50+
4. Another dialog appears saying `Local branch is up to date with 'branch name'`. Select `ok`.
51+
<img src="images/success-pull-changes.png" alt="Changes pulled"/>
52+
53+

0 commit comments

Comments
 (0)