This is the Contribution Guide for Roach PHP. Please read this document carefully before opening an issue or a pull request.
Before contributing to the project, please read our Code of Conduct.
Before you submit an issue, please search the issue tracker. An issue for your problem might already exist and the discussion might inform you of workarounds readily available.
You can file new issues by selecting an issue template and filling out the necessary information.
If you intend to change the public API or make any non-trivial changes to the implementation, make sure to create an issue first. This will let us discuss a proposal before you put significant effort into it.
If you're only fixing a bug or a typo, it's fine to submit a pull request right away without creating an issue, but make sure it contains a clear and concise description of the bug.
Before you start working on an issue make sure that it has been accepted
(indicated by an accepted
label) and that no one has
claimed it yet. Otherwise, you may duplicate other people's efforts. If somebody
claims an issue but doesn't follow up for more than two weeks, it’s fine to take
it over, but you should still leave a comment. You should also leave a comment
on any issue you're working on, to let others know.
Roach follows semantic versioning.
- Fork the roach-php/core repo.
- In your forked repo, create a new branch for your changes:
git checkout -b my-fix-branch main
- Update the code. Make sure that all your changes are covered by tests.
- Commit your changes using a descriptive commit message that follows the
Angular Commit Message Conventions.
git commit --all
- Push your branch to GitHub:
git push origin my-fix-branch
- In GitHub, send a pull request to the main branch.
- Make required updates to the code.
- Create a fixup commit and push it to your GitHub repo:
git commit --all --fixup HEAD git push
This Contribution Guide was adapted from the Motion Canvas Contribution guide