|
| 1 | +============ |
| 2 | +Contributing |
| 3 | +============ |
| 4 | + |
| 5 | +Contributions are welcome, and they are greatly appreciated! Every |
| 6 | +little bit helps, and credit will always be given. |
| 7 | + |
| 8 | +Bug reports |
| 9 | +=========== |
| 10 | + |
| 11 | +When `reporting a bug <https://github.com/accraze/python-livingdocs/issues>`_ please include: |
| 12 | + |
| 13 | + * Your operating system name and version. |
| 14 | + * Any details about your local setup that might be helpful in troubleshooting. |
| 15 | + * Detailed steps to reproduce the bug. |
| 16 | + |
| 17 | +Documentation improvements |
| 18 | +========================== |
| 19 | + |
| 20 | +Living Docs could always use more documentation, whether as part of the |
| 21 | +official Living Docs docs, in docstrings, or even on the web in blog posts, |
| 22 | +articles, and such. |
| 23 | + |
| 24 | +Feature requests and feedback |
| 25 | +============================= |
| 26 | + |
| 27 | +The best way to send feedback is to file an issue at https://github.com/accraze/python-livingdocs/issues. |
| 28 | + |
| 29 | +If you are proposing a feature: |
| 30 | + |
| 31 | +* Explain in detail how it would work. |
| 32 | +* Keep the scope as narrow as possible, to make it easier to implement. |
| 33 | +* Remember that this is a volunteer-driven project, and that code contributions are welcome :) |
| 34 | + |
| 35 | +Development |
| 36 | +=========== |
| 37 | + |
| 38 | +To set up `python-livingdocs` for local development: |
| 39 | + |
| 40 | +1. Fork `python-livingdocs <https://github.com/accraze/python-livingdocs>`_ |
| 41 | + (look for the "Fork" button). |
| 42 | +2. Clone your fork locally:: |
| 43 | + |
| 44 | + git clone git@github.com:your_name_here/python-livingdocs.git |
| 45 | + |
| 46 | +3. Create a branch for local development:: |
| 47 | + |
| 48 | + git checkout -b name-of-your-bugfix-or-feature |
| 49 | + |
| 50 | + Now you can make your changes locally. |
| 51 | + |
| 52 | +4. When you're done making changes, run all the checks, doc builder and spell checker with `tox <http://tox.readthedocs.org/en/latest/install.html>`_ one command:: |
| 53 | + |
| 54 | + tox |
| 55 | + |
| 56 | +5. Commit your changes and push your branch to GitHub:: |
| 57 | + |
| 58 | + git add . |
| 59 | + git commit -m "Your detailed description of your changes." |
| 60 | + git push origin name-of-your-bugfix-or-feature |
| 61 | + |
| 62 | +6. Submit a pull request through the GitHub website. |
| 63 | + |
| 64 | +Pull Request Guidelines |
| 65 | +----------------------- |
| 66 | + |
| 67 | +If you need some code review or feedback while you're developing the code just make the pull request. |
| 68 | + |
| 69 | +For merging, you should: |
| 70 | + |
| 71 | +1. Include passing tests (run ``tox``) [1]_. |
| 72 | +2. Update documentation when there's new API, functionality etc. |
| 73 | +3. Add a note to ``CHANGELOG.rst`` about the changes. |
| 74 | +4. Add yourself to ``AUTHORS.rst``. |
| 75 | + |
| 76 | +.. [1] If you don't have all the necessary python versions available locally you can rely on Travis - it will |
| 77 | + `run the tests <https://travis-ci.org/accraze/python-livingdocs/pull_requests>`_ for each change you add in the pull request. |
| 78 | +
|
| 79 | + It will be slower though ... |
| 80 | +
|
| 81 | +Tips |
| 82 | +---- |
| 83 | + |
| 84 | +To run a subset of tests:: |
| 85 | + |
| 86 | + tox -e envname -- py.test -k test_myfeature |
| 87 | + |
| 88 | +To run all the test environments in *parallel* (you need to ``pip install detox``):: |
| 89 | + |
| 90 | + detox |
0 commit comments