Contributing to Roots Theme
A bug is a demonstrable problem that is caused by the code in the repository.
Please read the following guidelines for reporting bugs: Please read the following guidelines before you report an issue:
Use the GitHub issue search — check if the issue has already been reported. If it has been, please comment on the existing issue.
Check if the issue has been fixed — the latest
masteror development branch may already contain a fix.
Isolate the problem to Roots — make sure that the code in the Roots repository is definitely responsible for the issue. Switch to a default WordPress theme to confirm problems before reporting an issue. Any issues related to HTML5 Boilerplate or Bootstrap should be reported to their respected repositories.
Please try to be as detailed as possible in your report too. What is your environment? What steps will reproduce the issue? What browser(s) and OS experience the problem? What would you expect to be the outcome? All these details will help people to assess and fix any potential bugs.
Example of a good bug report:
Short and descriptive title
A summary of the issue and the server OS environment in which it occurs. If suitable, include the steps required to reproduce the bug.
- This is the first step
- This is the second step
- Further steps, etc.
Any other information you want to share that is relevant to the issue being reported. This might include the lines of code that you have identified as causing the bug, and potential solutions (and your opinions on their merits).
A good bug report shouldn't leave people needing to chase you up to get further information that is required to assess or fix the bug.
Good pull requests — patches, improvements, new features — are a fantastic help. They should remain focused in scope and avoid containing unrelated commits.
If your contribution involves a significant amount of work or substantial changes to any part of the project, please open an issue to discuss it first.
Please follow this process; it's the best way to get your work included in the project:
Fork the project.
Clone your fork (
git clone https://github.com/<your-username>/roots.git).
git remote add upstream https://github.com/retlehs/roots.git).
Get the latest changes from upstream (e.g.
git pull upstream <dev-branch>).
Create a new topic branch to contain your feature, change, or fix (
git checkout -b <topic-branch-name>).
Make sure that your changes adhere to the current coding conventions used throughout the project - indentation, accurate comments, etc. Please update any documentation that is relevant to the change you are making.
Commit your changes in logical chunks; use git's interactive rebase feature to tidy up your commits before making them public. Please adhere to these git commit message guidelines or your pull request is unlikely be merged into the main project.
Locally merge (or rebase) the upstream branch into your topic branch.
Push your topic branch up to your fork (
git push origin <topic-branch-name>).
Open a Pull Request with a clear title and description. Please mention which browsers you tested in.