-
Notifications
You must be signed in to change notification settings - Fork 0
Commit Guidelines
Michel Pawlak edited this page Mar 14, 2017
·
3 revisions
- when committing new files to the codebase, run the command that adds missing license headers (see below)
- use wellformed commit messages (see below)
- if possible do not mix quality improvement commits with functional modifications commits
When adding new files, the have Maven build won't pass if they don't include expected license headers. All QualInsight projects are configured in order to ease the task of adding missing license headers. All you have to do is to run the following command:
mvn license:format
A wellformed commit message respects this template: <imperative verb> <concise subject> #<issue id>
.
Examples:
improve documentation #12
add unit tests #12
lower method complexity #12
Please avoid this kind of commit message:
I improved the documentation
#12
unit tests
#12 lower method complexity
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/.
- Home
- Contribution Process
- Guidelines
- Architecture
- Development
- Error Handling
- Logging
- Documentation
- Testing
- Maven
- Commit
- Pull Request