-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail build if commit naming convention is not met #436
Comments
@0xdiba any other ideas here? :) |
Is pre-commit hooks an opt-in sort of thing? I create many commits that do not follow this rule during the development process. |
hmm good point, that would probably not be a good idea. Maybe just something that's run in CI then? Found this, maybe we can reuse this or write something similar https://github.com/conventional-changelog/commitlint/blob/master/docs/reference-rules.md |
yeh! good idea @alenkacz . i think we have at least a few unwritten style guidelines (e.g. @ivotron ^ what do you think |
commitlint seems really cool! I think we should adopt it. I'll look deeper into it |
There's a convention for commit naming - all commits should be prefixed with component/sub-component name. It would be nice to have this convention enforced so that it's easy to follow for new contributors.
We could use pre-commit hook or at least start with a github action validating that.
JIRA Link: CORE-583
The text was updated successfully, but these errors were encountered: