aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2017-06-29 19:35:33 -0400
committerJack Humbert <jack.humb@gmail.com>2017-06-29 19:35:33 -0400
commitb139633f89c45ef26d43732e94dad3e3fcb8fa60 (patch)
tree0df4ad5834ee56da9b2d85c6adb44387b703c156
parent7da94ac51bf77d74b42ab63c06358ff59072289b (diff)
downloadqmk_firmware-b139633f89c45ef26d43732e94dad3e3fcb8fa60.tar.gz
qmk_firmware-b139633f89c45ef26d43732e94dad3e3fcb8fa60.zip
adds how to github
-rw-r--r--docs/how_to_github.md64
1 files changed, 64 insertions, 0 deletions
diff --git a/docs/how_to_github.md b/docs/how_to_github.md
new file mode 100644
index 000000000..2f3da42fd
--- /dev/null
+++ b/docs/how_to_github.md
@@ -0,0 +1,64 @@
1# How to use Github with QMK
2
3{% hint style='info' %}
4This guide assumes you're somewhat comfortable with running things at the command line, and have git installed on your system.
5{% endhint %}
6
7Start 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
9![Fork on Github](http://i.imgur.com/8Toomz4.jpg)
10
11If you're apart 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.
12
13From there, click the "Clone or Download" button:
14
15![Download from Github](http://i.imgur.com/N1NYcSz.jpg)
16
17And be sure to select "HTTPS", and select the link and copy it:
18
19![HTTPS link](http://i.imgur.com/eGO0ohO.jpg)
20
21From here, enter `git clone ` into the command line, and then paste your link:
22
23```
24**[terminal]
25**[prompt you@computer]**[path ~]**[delimiter $ ]**[command git clone https://github.com/whoeveryouare/qmk_firmware.git]
26Cloning into 'qmk_firmware'...
27remote: Counting objects: 46625, done.
28remote: Compressing objects: 100% (2/2), done.
29remote: Total 46625 (delta 0), reused 0 (delta 0), pack-reused 46623
30Receiving objects: 100% (46625/46625), 84.47 MiB | 3.14 MiB/s, done.
31Resolving deltas: 100% (29362/29362), done.
32Checking out files: 100% (2799/2799), done.
33**[prompt you@computer]**[path ~]**[delimiter $ ]
34```
35
36From here, you can add your keymap, compile it and flash it to your board. Once you're happy with your changes, you can add, commit, and push them to your fork like this:
37
38```
39**[terminal]
40**[prompt you@computer]**[path ~/qmk_firmware]**[delimiter $ ]**[command git add .]
41**[prompt you@computer]**[path ~/qmk_firmware]**[delimiter $ ]**[command git commit -m "adding my keymap"]
42[master cccb1608] adding my keymap
43 1 file changed, 1 insertion(+)
44 create mode 100644 keyboards/planck/keymaps/mine/keymap.c
45**[prompt you@computer]**[path ~/qmk_firmware]**[delimiter $ ]**[command git push]
46Counting objects: 1, done.
47Delta compression using up to 4 threads.
48Compressing objects: 100% (1/1), done.
49Writing objects: 100% (1/1), 1.64 KiB | 0 bytes/s, done.
50Total 1 (delta 1), reused 0 (delta 0)
51remote: Resolving deltas: 100% (1/1), completed with 1 local objects.
52To https://github.com/whoeveryouare/qmk_firmware.git
53 + 20043e64...7da94ac5 master -> master
54```
55
56If you go back to your fork on Github, you can create a "New Pull Request" by clicking this button:
57
58![New Pull Request](http://i.imgur.com/DxMHpJ8.jpg)
59
60From here, you'll be able to see exactly what you've committed - if it all looks good, you can finalize it by clicking "Create Pull Request":
61
62![Create Pull Request](http://i.imgur.com/Ojydlaj.jpg)
63
64From here, we may talk to you about your changes, ask that you make changes as we see fit, and eventually accept it! Thanks for contributing to QMK :) \ No newline at end of file