You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 13, 2019. It is now read-only.
Although we purposefully do not want much configuration (as the goal is to standardise commit message format across our projects), I can see some areas that would be useful:
Allowed project short-codes:
Currently we just check that there's some text where it should be. In reality for a specific project you'll want to lock it down to only allowing commit messages with the specified project code. e.g. where a ticket is actually TESTPROJ-123 the commit may accidentally contain TESTPROJECT-123 which would be considered valid.
Although we purposefully do not want much configuration (as the goal is to standardise commit message format across our projects), I can see some areas that would be useful:
Allowed project short-codes:
Currently we just check that there's some text where it should be. In reality for a specific project you'll want to lock it down to only allowing commit messages with the specified project code. e.g. where a ticket is actually
TESTPROJ-123
the commit may accidentally containTESTPROJECT-123
which would be considered valid.Example config:
Allowed ticketing systems
Most projects will just use JIRA, some will also use Zendesk. I'm not sure if we use any others, but would be a good idea to:
Z#
andJ#
Example config:
============
Anything else? We could allow commit types to be configured, but I think there's more value in enforcing consistency on that front.
The text was updated successfully, but these errors were encountered: