We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In GitLab under Settings -> Repository -> Push Rules you can set Require expression in commit messages. I assume GitHub has a similar feature.
Require expression in commit messages
A regex for ACN would need to be permissive enough to allow local extensions but require the extension.
Here's the regex I'm currently using: ^(([[:lower:]] )|([[:upper:]] )|([[:upper:]]!! )|([[:upper:]]\*\* ))|(\*\*\*).
^(([[:lower:]] )|([[:upper:]] )|([[:upper:]]!! )|([[:upper:]]\*\* ))|(\*\*\*)
When we add this guidance we could use CI to test it. Here are some test cases + questions:
The text was updated successfully, but these errors were encountered:
I like making a suggestion that people include a push rule.
I think v2 ( #43 as the first attempt ) should make that easier.
Sorry, something went wrong.
Cool. Once v2 settles and ships, I plan to send a PR with the regex guidance.
No branches or pull requests
In GitLab under Settings -> Repository -> Push Rules you can set
Require expression in commit messages
. I assume GitHub has a similar feature.A regex for ACN would need to be permissive enough to allow local extensions but require the extension.
Here's the regex I'm currently using:
^(([[:lower:]] )|([[:upper:]] )|([[:upper:]]!! )|([[:upper:]]\*\* ))|(\*\*\*)
.When we add this guidance we could use CI to test it. Here are some test cases + questions:
The text was updated successfully, but these errors were encountered: