Guidance for commit message regex

[JayBazuzi]

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:

[arlobelshee]

I like making a suggestion that people include a push rule.

I think v2 ( #43 as the first attempt ) should make that easier.

[JayBazuzi]

Cool. Once v2 settles and ships, I plan to send a PR with the regex guidance.

[arlobelshee]

@JayBazuzi , can you add the guidance for V2 and close this? Also, does such a regex interfere with using conventional commits on merge commits?

[JayBazuzi]

PR sent with a regex for just ACN. Yes, it would conflict with Conventional Commits. Possible next steps:

• detailed examples of how to set up a hook/action/push rule/etc.
• generalize the regex to allow either ACN or Conventional Commits
• guidance for how to apply the rule in a branch and not on main, to allow CC and tool-generated PRs