Changes between Version 1 and Version 2 of DevNotes/Obsolete/CommitMessage
- Timestamp:
- Apr 9, 2017 8:45:41 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DevNotes/Obsolete/CommitMessage
v1 v2 1 To refer to trac tickets in commit messages the basic syntax is of the form [command] [ticketreference]. A colon between the command and the ticket reference is allowed. The ticketreference also allows to list multiple ticket numbers separated by spaces and/or comma. The word 'and' is also allowed between ticket numbers. 1 To refer to trac tickets in commit messages the basic syntax is of the form [command] [ticketreference]. A colon between the command and the ticket reference is allowed. The ticketreference also allows to list multiple ticket numbers separated by spaces and/or comma. The word 'and' is also allowed between ticket numbers. The allowed syntaxes are given below. 2 2 3 One can optionally refer to tickets with the following words 3 To close a ticket from a commit message: 4 {{{ 5 closes #ticketno 6 fixes #ticketno 7 e.g. this closes #10 8 }}} 4 9 5 ticket, issue, bug 6 Examples (note: not verified!): 10 To reference a ticket in a commit message: 11 {{{ 12 addresses #ticketno 13 re #ticketno 14 references #ticketno 15 refs #ticketno 16 see #ticketno 17 e.g. this addresses #10 and #25 18 }}} 7 19 8 {{{ 9 close #10 10 closed: #10 11 closes #10 12 closes ticket:10 13 fixes #10 14 fixes bug:10 15 see issue 5 16 references #5, #6 17 fixes #10 and #11 18 }}} 20 A bare reference to a ticket (e.g. !#48) will not trigger a ticket update on trac. 21 22 More info on how to use is in the docs: https://trac.edgewall.org/wiki/CommitTicketUpdater#Usage