Ensure the bug was not already reported by searching on Issues.
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
If possible, use the relevant bug report templates to create the issue. Simply copy the content of the appropriate template into a .rb file, make the necessary changes to demonstrate the issue, and paste the content into the issue description:
For more detailed information on submitting a bug report and creating an issue, visit our Wiki guidelines.
Open a new GitHub pull request with the patch.
Ensure the PR description clearly describes the problem and solution. Include the relevant issue number by including a issue hash tag if applicable.
Before submitting, please read the Contributing Wiki for Developers and Programmers to know more about coding conventions and benchmarks.
-
Did you fix whitespace, format code, or make a purely cosmetic patch? Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability will generally not be accepted.
-
Do you intend to add a new feature or change an existing one? Suggest your change in the forum and start writing code.
-
Do not open an issue on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for bug reports and fixes.
Do you have questions about the source code? Ask any question about how to use, check the forum.
Do you want to contribute to the documentation, apply here using a wiki request?
This Plugin is a volunteer effort. We encourage you to pitch in and join the team!