@@ -51,3 +51,26 @@ It would also be very helpful to install the SonarLint plugin in your IDE and fi
5151SonarLint issues before pushing a PR. We're aware that the current state of the code raises a lot of
5252SonarLint issues out of the box, but any help in reducing that is appreciated. More importantly we
5353don't increase that technical debt.
54+
55+ ###Commit messages
56+
57+ This project uses the [ Conventional Commits] ( https://www.conventionalcommits.org ) specification for commit messages.
58+ The CI pipeline validates that commit messages adhere to the specification using
59+ [ commitlint] ( https://github.com/conventional-changelog/commitlint ) .
60+
61+ ** Note** : * Historical commits, made before applying this convention may not fulfill the requirements of the
62+ specification. These commits are exempt from this check.*
63+
64+ To check commit messages before committing, go to the ` commitlint ` folder and run ` npm ci && npm run add-commitlint-git-hook `
65+ (you will need NodeJS installed on your machine). This command sets up a git hook to run commitlint before each commit,
66+ to prevent committing with invalid commit messages in the first place.
67+
68+ ** Note** : * Please always use ` npm ci ` instead of ` install ` to prevent unwanted changes to ` package-lock.json ` .*
69+
70+ To remove the git hook, just delete the ` commitlint/.husky ` folder.
71+
72+ As for the optional scope part of the commit message:
73+ - if your commit addresses an issue, please refer the issue number in the scope - e.g. ` fix(#123): ... `
74+ - otherwise, if applicable, please use the modified / affected subproject name, without the repetitive prefix/postfix
75+ parts (like ` graphql-kickstart-spring-boot ` , ` spring-boot-starter ` or ` autoconfigure ` ) - e.g. ` feat(webflux): ... `
76+
0 commit comments