|
1 | 1 | # How to contribute
|
2 |
| - |
3 |
| -Heya, Luke here. It's awesome that you want to help contribute to CloudBot! |
4 |
| -This should be as easy as possible for you but there are a few things to consider when contributing. |
5 |
| - |
6 |
| -The following guidelines for contribution should be followed if you want to submit a pull request. If you have any troubles, just come and ask us for help on our IRC channel. |
| 2 | +The following guidelines for contribution should be followed if you want to |
| 3 | +submit a pull request. |
7 | 4 |
|
8 | 5 | ## Basic Overview
|
9 |
| - |
10 |
| -* Read [Github documentation](http://help.github.com/) and [Pull Request documentation](http://help.github.com/send-pull-requests/) |
11 |
| -* Fork the repository |
12 |
| -* Edit the files, add new files |
13 |
| -* Check the files with [`pep8`](https://pypi.python.org/pypi/pep8), fix any reported errors |
14 |
| -* Check that the files work as expected in CloudBot |
15 |
| -* Create a new branch with a descriptive name for your feature (optional) |
16 |
| -* Commit changes, push to your fork on GitHub |
17 |
| -* Create a new pull request, provide a short summary of changes in the title line, with more information in the description field. |
18 |
| -* After submitting the pull request, join the IRC channel (irc.esper.net #cloudbot) and give us a link so we know you submitted it. |
19 |
| -* After discussion, your pull request will be accepted or rejected. |
20 |
| - |
21 |
| -## How to prepare |
22 |
| - |
23 |
| -* You need a [GitHub account](https://github.com/signup/free) |
24 |
| -* Submit an [issue ticket](https://github.com/ClouDev/CloudBot/issues) for your issue if there is no one yet. |
25 |
| - * Try to describe the issue and include steps to reproduce if it's a bug. |
26 |
| -* If you are able and want to fix this, fork the repository on GitHub |
27 |
| - |
28 |
| -## Make Changes |
29 |
| - |
30 |
| -* In your forked repository, create a topic branch for your upcoming patch. (optional) |
31 |
| -* Make sure you stick to the coding style that is used already. |
32 |
| -* Make use of the [`.editorconfig`](http://editorconfig.org/) file. |
33 |
| -* Make commits that make sense and describe them properly. |
34 |
| -* Check for unnecessary whitespace with `git diff --check` before committing. |
35 |
| -* Check your changes with [`pep8`](https://pypi.python.org/pypi/pep8). You can usually ignore messages about line length, but we like to keep lines shorter then 120 characters if at all possible. |
| 6 | +1. Read [Github documentation](http://help.github.com/) and [Pull Request documentation](http://help.github.com/send-pull-requests/) |
| 7 | +2. Fork the repository |
| 8 | +3. Create a new branch with a descriptive name for your feature |
| 9 | +4. Edit the files, add new files |
| 10 | +5. Add tests for your changes or new feature |
| 11 | +6. [Use pre-commit] to check that your changes follow the coding style |
| 12 | +7. Add an entry in the [CHANGELOG] |
| 13 | +8. Commit changes, push to your fork on GitHub |
| 14 | +9. Create a new pull request, provide a short summary of changes in the title line, with more information in the description field. |
| 15 | + |
| 16 | +## Use pre-commit |
| 17 | +This project uses [pre-commit] |
| 18 | +1. [Install pre-commit] |
| 19 | +2. Run `pre-commit install` to add it as a git precommit hook to run checks on each `git commit` in the repository |
| 20 | +3. Run `pre-commit run` before commiting, to check your changes easily |
36 | 21 |
|
37 | 22 | ## Submit Changes
|
38 |
| - |
39 |
| -* Push your changes to a topic branch in your fork of the repository. |
40 |
| -* Open a pull request to the original repository and choose the `python3.4` branch. |
41 |
| - _Advanced users may use [`hub`](https://github.com/defunkt/hub#git-pull-request) gem for that._ |
42 |
| -* If not done in commit messages (which you really should do) please reference and update your issue with the code changes. But _please do not close the issue yourself_. |
43 |
| -_Notice: You can [turn your previously filed issues into a pull-request here](http://issue2pr.herokuapp.com/)._ |
| 23 | +1. Push your changes to a topic branch in your fork of the repository. |
| 24 | +2. Open a pull request to the original repository and choose the `gonzobot` branch. |
| 25 | +3. Correct any issues shown by the automated checks |
| 26 | +4. Join the [IRC channel] if you have any questions or concerns, or if you just want to talk with other devs |
44 | 27 |
|
45 | 28 | # Additional Resources
|
46 |
| - |
47 | 29 | * [General GitHub documentation](http://help.github.com/)
|
48 | 30 | * [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
|
49 | 31 | * [Read the Issue Guidelines by @necolas](https://github.com/necolas/issue-guidelines/blob/master/CONTRIBUTING.md) for more details
|
50 | 32 | * [This CONTRIBUTING.md from here](https://github.com/anselmh/CONTRIBUTING.md)
|
| 33 | + |
| 34 | +[pre-commit]: https://pre-commit.com/ |
| 35 | +[Install pre-commit]: https://pre-commit.com/#install |
| 36 | +[Use pre-commit]: #use-pre-commit |
| 37 | +[CHANGELOG]: CHANGELOG.md |
| 38 | +[IRC channel]: README.md#support |
0 commit comments