4 ms·
Mine is "[JIRA_TICKET] Add something" It's simple and worked well for us so far. Less rules, more information, and developers are free to use their words to ex
by revskill 5y ago
Mine is
"[JIRA_TICKET] Add something"
It's simple and worked well for us so far. Less rules, more information, and developers are free to use their words to express intention of changes instead of nonsense (feat, fix,....)
- tremon 5y agoHave you gone through a ticketing system change yet with a developer team? I've seen several, and not once was "we must import the old PR's/issues/features into the new system" given any serious consideration. Conversely, every source control system migration I've seen took great pains to preserve the committer, the date and the full commit message of each separate commit. Point being, in a few years all your [external references] will be useless. Can your commit messages explain the commit context on their own?
- revskill 5y agoOK, my question is, no effective commit message system exists without a consistent ticket system. A ticket reference gives you all you need. You see it in every line of code, from there you know the reason for that code to be written, it could include a reference to slack discussion url,...