Contributing to Transit
Want to get involved? Thanks! There are plenty of ways to help!
A bug is a demonstrable problem that is caused by the code in the repository.
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 demonstrable problem — make sure that the code in the project's repository is definitely responsible for the issue. Create a reduced test case - an extremely simple and immediately viewable example of the issue.
Include a live example — provide a link to your reduced test case when appropriate (e.g. if the issue is related to (front-end technologies). Please use jsFiddle to host examples.
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 browser/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.
<url>(a link to the reduced test case)
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.
Responding to issues
Feel free to respond to other people's issues! Some people may be reporting issues that can easily be solved even without modification to the project's code.
You can also help by verifying issues reported.
The 'help wanted' tag
Some issues are tagged with the 'help wanted' tag. These issues often:
- are missing an actual implementation, or
- need people's help in verifying and replicating the issue, or
- need test cases.
If you would like to contribute code and don't have any specific issue you want to fix, this would be a good place to start looking at!
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>/html5-boilerplate.git).
git remote add upstream https://github.com/rstacruz/jquery.transit.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.
This contributing guide has been adapted from HTML5 boilerplate's guide.