Contributing to Sorter
Thank you, for taking your time to contribute. 👍
The following is a set of guidelines for contributing to Sorter and its components. These are mostly guidelines, not rules. Use your best judgment.
This project and its participants are governed by a Code of Conduct. By participating, you are expected to uphold this code. Any unacceptable behavior shall not be tolerated.
This section guides you through submitting a bug report for Sorter. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
Bugs and issues are reported here. Before reporting a bug, please check that it has not yet been reported. Be sure to assign the bug label to your issue. Kindly include as much detail as you can while reporting the bug, including details about your environment such as:
- Which version of Sorter you are using? You can get the exact version by checking Help > About.
- What's the name and version of the OS you're using?
- Is your OS x86 or x64, or other? Include as much details as possible.
Note: If you find a Closed issue that seems similar to what you are experiencing, open a new issue and include a link to the original issue in the body of your new one.
This section guides you through submitting an enhancement suggestion for Sorter, including completely new features and minor improvements to existing functionality. Following these guidelines helps maintainers and the community understand your suggestion and find related suggestions.
Enhancement suggestions are reported here. Before creating an enhancement suggestion, please check that you are using the latest version of Sorter. Also check that your suggestion has not yet been made. If it has, add a comment, or a note, to the existing issue. Be sure to assign the enhancement label to your issue and include as much detail as possible.
Before making changes to this repository, check that the development branch does not feature your enhancements.
Recommended: Go through the style guides before proceeding.
- Fork this repository to make your own copy of this project.
- Checkout from the development branch.
- Make your changes to the projects.
- Create tests for your changes.
- Merge to the development branch.
- Submit a pull request on your proposed changes. Include full and comprehensive details on your changes.
Know how to write good commit messages.
- Use the present tense ("Add feature" not "Added feature")
- Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
- Limit the first line to 50 characters or less
- Reference issues and pull requests liberally after the first line
Use 4 spaces, NOT tabs.
Please open an issue if you have further suggestions for this document and/or the Code of Conduct