Laravel AT Protocol Client (alpha & unstable)
1# Contributing
2
3Contributions are welcome and will be fully credited.
4
5Contributions are accepted via Pull Requests on [Github](https://github.com/social-dept/atp-client).
6
7# Things you could do
8If you want to contribute but do not know where to start, this list provides some starting points.
9- Add license text
10- Remove rewriteRules.php
11- Set up TravisCI, StyleCI, ScrutinizerCI
12- Write a comprehensive ReadMe
13
14## Pull Requests
15
16- **Add tests!** - Your patch won't be accepted if it doesn't have tests.
17
18- **Document any change in behaviour** - Make sure the `readme.md` and any other relevant documentation are kept up-to-date.
19
20- **Consider our release cycle** - We try to follow [SemVer v2.0.0](http://semver.org/). Randomly breaking public APIs is not an option.
21
22- **One pull request per feature** - If you want to do more than one thing, send multiple pull requests.
23
24- **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting.
25
26
27**Happy coding**!