I found this somewhere, but somehow I can't find the link to the page
that describes this. Luckily, I sent this email out to my teammates a
while back:
example format:
command #1
command #1, #2
command #1 & #2
command #1 and #2
Where "command" can take on the following forms: closes, fixes,
references, refs, addresses, or re.
closes, fixes
The specified issue numbers are closed with the contents of this
commit message being added to it.
references, refs, addresses, re
The specified issue numbers are left in their current status, but
the contents of this commit message are added to their notes.
Example commit message:
This references #8. The final fix won't be until later. OK, I lied.
This is really just a test commit.
The above message will then be appended to the comments section of
ticket #8. The said ticket will remain open and unchanged though.
On 4/6/06, geoffrey <[EMAIL PROTECTED]> wrote:
> Did I dream this? I don't find any information on it anywhere, but I
> recall someone in the past telling me you could word your commit
> messages in such a way that Trac will understand the code being checked
> in is related to a particular ticket and change the ticket status to
> fixed/resolved. Is this true, or just one of my hallucinations? If it's
> true, how do I accomplish this feat. Thanks for any clue beatings.
>
> geoffrey
> _______________________________________________
> Trac mailing list
> [email protected]
> http://lists.edgewall.com/mailman/listinfo/trac
>
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac