Mercurial > hg
comparison CONTRIBUTING @ 30084:a492610a2fc1
contributing: add new file with a pointer to the wiki
This also includes what I consider to be the minimum set of steps
someone should be able to perform even if they can't run the
testsuite. Hopefully this will help new contributors know to at least
run the two checkers that find most things that (in my experience)
require manual cleanup.
| author | Augie Fackler <augie@google.com> |
|---|---|
| date | Sat, 08 Oct 2016 10:39:00 -0400 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 30083:bd1f043d1ea3 | 30084:a492610a2fc1 |
|---|---|
| 1 Our full contribution guidelines are in our wiki, please see: | |
| 2 | |
| 3 https://www.mercurial-scm.org/wiki/ContributingChanges | |
| 4 | |
| 5 If you just want a checklist to follow, you can go straight to | |
| 6 | |
| 7 https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist | |
| 8 | |
| 9 If you can't run the entire testsuite for some reason (it can be | |
| 10 difficult on Windows), please at least run `contrib/check-code.py` on | |
| 11 any files you've modified and run `python contrib/check-commit` on any | |
| 12 commits you've made (for example, `python contrib/check-commit | |
| 13 273ce12ad8f1` will report some style violations on a very old commit). |