on master help sign in
Updates to contributing guidelines.
a306c33Jan de Muijnck-Hughes
CONTRIBUTING.md+37−13
@@ -30,34 +30,54 @@ Please clean up any messes that you find, and don't leave behind new messes for
30Idris developers and hackers try to adhere to something similar to the [successful git branching model](http://nvie.com/posts/a-successful-git-branching-model/).
30Idris developers and hackers try to adhere to something similar to the [successful git branching model](http://nvie.com/posts/a-successful-git-branching-model/).
31The steps are straightforward.
31The steps are straightforward.
32
32
33+### New contributors
34+
33For those new to the project:
35For those new to the project:
34
36
35−1. Fork the `idris-dev` repo e.g.
37+1. Fork our [main development repository](https://github.com/idris-lang/Idris-dev) `idris-dev` on github e.g.
38+2. Clone your fork to your local machine:
39+
40+```
41+$ git clone git@github.com/<your github user name>/Idris-dev.git
42+```
43+
44+3. Add `idris-lang/Idris-dev` as a remote upstream
36
45
37− $ git clone git@github.com/<your github user name>/Idris-dev.git
46+```
38− $ git remote add upstream git@github.com:idris-lang/Idris-dev.git
47+$ git remote add upstream git@github.com:idris-lang/Idris-dev.git
48+```
49+
50+### Existing Contributors
39
51
40For those already contributing to the project:
52For those already contributing to the project:
41
53
42−1. Ensure your existing clone is up-to-date with current HEAD e.g.
54+1. Ensure your existing clone is up-to-date with current `HEAD` e.g.
55+
56+```
57+$ git fetch upstream
58+$ git merge upstream/master
59+```
43
60
44− $ git fetch upstream
61+### Remaining Steps
45− $ git merge upstream/master
46
62
47−The remaining steps are the same:
63+The remaining steps are the same for both new and existing contributors:
48
64
491. Create, and checkout onto, a topic branch on which to base you work.
651. Create, and checkout onto, a topic branch on which to base you work.
50 * This is typically the master branch.
66 * This is typically the master branch.
51 * For your own sanity, please avoid working on the `master` branch.
67 * For your own sanity, please avoid working on the `master` branch.
52
68
69+```
53− $ git branch fix/master/my_contrib master
70+$ git branch fix/master/my_contrib master
54− $ git checkout fix/master/my_contrib
71+$ git checkout fix/master/my_contrib
72+```
55
73
561. Make commits of logical units.
741. Make commits of logical units.
571. Check for unnecessary whitespace with
751. Check for unnecessary whitespace with
58
76
77+```
59− $ git diff --check
78+$ git diff --check
60−
79+```
80+
611. Make sure your commit messages are along the lines of:
811. Make sure your commit messages are along the lines of:
62
82
63 Short (50 chars or less) summary of changes
83 Short (50 chars or less) summary of changes
@@ -79,11 +99,15 @@ The remaining steps are the same:
791. Make sure you have added any necessary tests for your changes.
991. Make sure you have added any necessary tests for your changes.
801. Run all the tests to assure nothing else was accidentally broken.
1001. Run all the tests to assure nothing else was accidentally broken.
81
101
102+```
82− $ make test
103+$ make test
104+```
83
105
841. Push your changes to a topic branch in your fork of the repository.
1061. Push your changes to a topic branch in your fork of the repository.
85
107
108+```
86− $ git push origin fix/master/my_contrib
109+$ git push origin fix/master/my_contrib
110+```
87
111
881. Go to GitHub and submit a pull request to `idris-dev`
1121. Go to GitHub and submit a pull request to `idris-dev`
89
113
CONTRIBUTORS+2
@@ -15,6 +15,7 @@ Hannes Mehnert
15Mekeor Melire
15Mekeor Melire
16Melissa Mozifian
16Melissa Mozifian
17Dominic Mulligan
17Dominic Mulligan
18+Jan de Muijnck-Hughes
18raichoo
19raichoo
19Tom Prince
20Tom Prince
20Seo Sanghyeon
21Seo Sanghyeon
@@ -26,3 +27,4 @@ Leif Warner
26Daniel Waterworth
27Daniel Waterworth
27Jonas Westerlund
28Jonas Westerlund
28Reynir Reynisson
29Reynir Reynisson
30+