Skip to content

Commit 37e6659

Browse files
committed
f7
1 parent 070ae42 commit 37e6659

File tree

2 files changed

+10
-7
lines changed

2 files changed

+10
-7
lines changed

handson_branch.Rmd

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Fast-forward
9292
git revert HEAD
9393
```
9494

95-
- This pushes you into a unix text editor. The full explanation is tedious. Just type `Esc`, then `:wq` then `Enter`
95+
- This pushes you into a UNIX text editor. The full explanation is tedious. Just type `Esc`, then `:wq` then `Enter`
9696

9797
17. Commit and Push.
9898
1. Observe the visual representations of the version history
@@ -107,15 +107,15 @@ A full explanation of [git revert](https://git-scm.com/docs/git-revert) and [git
107107
For small changes, many people find a far simpler method is as follows...
108108

109109
1. At GitHub, click the "Commits" link
110-
1. Isolate the verion you need by clicking the `< >` link. This enables you to browse the repository at that point in history
110+
1. Isolate the version you need by clicking the `< >` link. This enables you to browse the repository at that point in history
111111
1. Navigate to the fine you need. Copy the file.
112112
1. Back in your editor, paste over the source version.
113113
Commit & Push
114114

115115

116116
## Roll back
117117

118-
The above example is a trivial example of how to employ rolling back to a previous version. Rolling back is complicated. Depending on the complexity of your project, it may be more crtical to leverage git commands during a roll-back. Software applications may be an example of this complexity. However, for simpler roll-backs, the simple explanations below may save you a lot of time for an operation which you would otherwise rarely perform.
118+
The above example is a trivial example of how to employ rolling back to a previous version. Rolling back is complicated. Depending on the complexity of your project, it may be more critical to leverage git commands during a roll-back. Software applications may be an example of this complexity. However, for simpler roll-backs, the simple explanations below may save you a lot of time for an operation which you would otherwise rarely perform.
119119

120120
### File
121121

handson_pr.Rmd

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,14 @@ When you fork a repository you make a copy of that repository on GitHub. The di
2020

2121
If you intend to submit modifications to some other repository by issuing a Pull Request, fork the repository first. Then clone the forked repository.
2222

23-
https://github.com/data-and-visualization/pr_hello-world
2423

25-
1. [Source] Make a test repository and have your parter `fork` your repository
24+
#### Exercise
25+
26+
1. [Source] Clone [this test repository](https://github.com/data-and-visualization/pr_hello-world
27+
)
28+
1. [Source] Have your partner `fork` your repository
2629
1. [Partner] After you forked above, `clone` your forked repository
27-
1. [Partner] Make some changse to your cloned [forked] repository. (e.g. add a file, edit the readme, etc.)
30+
1. [Partner] Make some changes to your cloned [forked] repository. (e.g. add a file, edit the readme, etc.)
2831
1. [Partner] Using the git commands you've already learned: add, commit, and push the changes
2932

3033

@@ -53,7 +56,7 @@ The GitHub Wiki is unique to your repository. Use it to lay out a roadmap of yo
5356

5457
## Issues on GitHub
5558

56-
The issues section is a good place to track bugs with your repository. You might even use this as a public todo list.
59+
The issues section is a good place to track bugs with your repository. You might even use this as a public to-do list.
5760

5861
## Remotes
5962

0 commit comments

Comments
 (0)