3 ms·
In a previous gig, we had a simple rule: there must be a ticket number with a certain format at the beginning of the commit message. A summary follows. The tic
by nandemo 11y ago
In a previous gig, we had a simple rule: there must be a ticket number with a certain format at the beginning of the commit message. A summary follows.
The ticket has pretty much all the info you need, so there's usually no need to write a very detailed commit message.
This essentially mandates tickets for every single commit, which might sound too process heavy for some people, but ticketing was part of our process anyway for other reasons (change management, compliance, etc).
In the rare event that a commit is not originated by a ticket, you can still cheat by writing a fake ticket number.
- dsr_ 11y agoIt ought to be a simple matter to start a new ticket and dump your work into it. A la the Joel Test, your ticketing system should: - open a new ticket on receipt of unknown email, sending back the ticket number - treat email with a proper subject prefix as a comment on an existing ticket, adding any attached files - easily merge two or more tickets, preserving both histories and redirecting all references to the old tickets to the new one - maintain metadata and ACLs for metadata - automatically re-open a ticket when a new comment or reply is received - require a message to close a ticket - provide summaries - be full-text searchable - track all history immutably - provide a method to associate many individual reports of the same problem