Contribution Process
We ask contributors to respect the following few steps when contributing to one of our projects:
- if you plan to fix a bug / add a new feature / help on a specific topic, please first create a GitHub issue in the project and explain what you plan to do.
- if your contribution implies consequent work, please first discuss with us the design of your contribution. This will ease the PR review and make sure that there will be no dispute concerning the design you have chosen.
- fork the project you want to contribute to
- create a feature branch for your contribution
- configure your IDE
- write code that respects coding guidelines and documentation guidelines
- write unit test respects testing guidelines
- analyze your code frequently using the latest SonarLint default configuration
- commit your changes respecting commit guidelines
- once you're done, make a wellformed pull request that respects pull request guidelines in order to ask us to merge back your branch to our project
QualInsight contribution guidelines by Michel Pawlak is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Permissions beyond the scope of this license may be available at http://www.qualinsight.com/.
