Commit Message Validation
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Having standard commit messages improves project hygiene and may simplify related processes. e.g. Using conventional commits, releases notes can be generated directly from the git messages. Existing solutions to enforce a standard commit are at best a band aid since they rely upon post commit processes, human interaction, or client hooks. This new feature allows project owners to enforce commit message formats based on a regex expression or a webhook.
Problem to solve
As a project owner, I want to enforce a standard commit message format. I use commit messages in multiple automated processes, such as release notes. Commit messages which break or fail to follow the defined format can break these process flows. The larger the teams, or the more the teams change, the more critical these breaks can be.
Intended users
Project owner/admin would define or select from prebuilt standard templates. Anyone pushing commits would be affected by having commits rejected when they fail to follow the standard format.
User experience goal
If a commit message fails to follow the standard, the commit push will fail. Note: This could have ripple effects to Gitlab UI such as MRs and editing files.
Proposal
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Free for regex and standard templates. Premium for using webhooks.