diff options
| author | Ryan <fauxpark@gmail.com> | 2020-05-26 12:43:14 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-05-25 19:43:14 -0700 |
| commit | e4823aadec24bca0ecfd1184562d27a49fd20544 (patch) | |
| tree | 66699e086fdd4b6c87bf2f83f4fae74c4e8ecded /docs/getting_started_github.md | |
| parent | 5c9906eb4fc569cd08d88dcd85ce9afaa5410ffb (diff) | |
| download | qmk_firmware-e4823aadec24bca0ecfd1184562d27a49fd20544.tar.gz qmk_firmware-e4823aadec24bca0ecfd1184562d27a49fd20544.zip | |
Fix capitalisation of "GitHub" (#9184)
Diffstat (limited to 'docs/getting_started_github.md')
| -rw-r--r-- | docs/getting_started_github.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/getting_started_github.md b/docs/getting_started_github.md index 07f523f57..ae594f68d 100644 --- a/docs/getting_started_github.md +++ b/docs/getting_started_github.md | |||
| @@ -1,16 +1,16 @@ | |||
| 1 | # How to Use Github with QMK | 1 | # How to Use GitHub with QMK |
| 2 | 2 | ||
| 3 | Github can be a little tricky to those that aren't familiar with it - this guide will walk through each step of forking, cloning, and submitting a pull request with QMK. | 3 | GitHub can be a little tricky to those that aren't familiar with it - this guide will walk through each step of forking, cloning, and submitting a pull request with QMK. |
| 4 | 4 | ||
| 5 | ?> This guide assumes you're somewhat comfortable with running things at the command line, and have git installed on your system. | 5 | ?> This guide assumes you're somewhat comfortable with running things at the command line, and have git installed on your system. |
| 6 | 6 | ||
| 7 | Start on the [QMK Github page](https://github.com/qmk/qmk_firmware), and you'll see a button in the upper right that says "Fork": | 7 | Start on the [QMK GitHub page](https://github.com/qmk/qmk_firmware), and you'll see a button in the upper right that says "Fork": |
| 8 | 8 | ||
| 9 |  | 9 |  |
| 10 | 10 | ||
| 11 | If you're a part of an organization, you'll need to choose which account to fork it to. In most circumstances, you'll want to fork it to your personal account. Once your fork is completed (sometimes this takes a little while), click the "Clone or Download" button: | 11 | If you're a part of an organization, you'll need to choose which account to fork it to. In most circumstances, you'll want to fork it to your personal account. Once your fork is completed (sometimes this takes a little while), click the "Clone or Download" button: |
| 12 | 12 | ||
| 13 |  | 13 |  |
| 14 | 14 | ||
| 15 | And be sure to select "HTTPS", and select the link and copy it: | 15 | And be sure to select "HTTPS", and select the link and copy it: |
| 16 | 16 | ||
| @@ -54,7 +54,7 @@ To https://github.com/whoeveryouare/qmk_firmware.git | |||
| 54 | + 20043e64...7da94ac5 master -> master | 54 | + 20043e64...7da94ac5 master -> master |
| 55 | ``` | 55 | ``` |
| 56 | 56 | ||
| 57 | Your changes now exist on your fork on Github - if you go back there (`https://github.com/<whoeveryouare>/qmk_firmware`), you can create a "New Pull Request" by clicking this button: | 57 | Your changes now exist on your fork on GitHub - if you go back there (`https://github.com/<whoeveryouare>/qmk_firmware`), you can create a "New Pull Request" by clicking this button: |
| 58 | 58 | ||
| 59 |  | 59 |  |
| 60 | 60 | ||