You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,20 +13,25 @@ If you are proposing new features, please discuss them with us in the [developme
13
13
## We Develop with Github
14
14
We use github to host code, to track issues and feature requests, as well as accept pull requests.
15
15
16
-
## We Use [Github Flow](https://guides.github.com/introduction/flow/index.html), So All Code Changes Happen Through Pull Requests
17
-
Pull requests are the best way to propose changes to the codebase (we use [Github Flow](https://guides.github.com/introduction/flow/index.html)). We actively welcome your pull requests:
16
+
## We Use [Git Flow](https://atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)
17
+

18
+
When contributing to this project please make sure you follow this and name your branches appropriately!
18
19
19
-
1. Fork the repo and create your branch from `master`.
20
+
## All Code Changes Happen Through Pull Requests
21
+
Make sure you know how Git Flow works before contributing!
22
+
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
23
+
24
+
1. Fork the repo and create your branch from `master` or `development` according to Git Flow.
20
25
2. If you've added code that should be tested, add tests.
21
26
3. If you've changed APIs, update the documentation.
22
27
4. Ensure the test suite passes.
23
28
5. Make sure your code lints.
24
29
6. Issue that pull request!
25
30
26
-
## Any contributions you make will be under the MIT Software License
27
-
In short, when you submit code changes, your submissions are understood to be under the same [MIT License](http://choosealicense.com/licenses/mit/) that covers the project. Feel free to contact the maintainers if that's a concern.
31
+
## Any contributions you make will be under the GNU Affero General Public License v3.0
32
+
In short, when you submit code changes, your submissions are understood to be under the same [GNU Affero General Public License v3.0](https://www.gnu.org/licenses/agpl-3.0.en.html) that covers the project. Feel free to contact the maintainers if that's a concern.
28
33
29
-
## Report bugs using Github's [issues](https://github.com/kyb3r/modmail/issues)
34
+
## Report bugs using [Github Issues](https://github.com/kyb3r/modmail/issues)
30
35
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](https://github.com/kyb3r/modmail/issues/new); it's that easy!
31
36
32
37
## Write bug reports with detail, background, and sample code
0 commit comments