I think git doesn't do that. The idea sounds interesting but i have a few questions: What if there are several IDs mentioned? What if no issue ID is mentioned at all?
Maybe we should think about an issues array that is parsed from the log at the same time as the modifications array (via the history parser). That way you could easily access the issue IDs at any step in the source control workflow without additional parsing work. The latest issue ID that was mentioned in the log would then be the one with the highest (or lowest) index... It would also be possible to incorporate a list of all issue IDs that were mentioned in the log since the last build in the commit message of the tag. Just some loud thinking... Kind regards, Daniel On Tue, 2010-09-28 at 14:16 -0400, Andy Levy wrote: > Here's my use case: When committing a tag, I want to be able to look > at the commit's log message & incorporate the change request ID > (parsed from the log message via RegEx) into the commit message of the > tag.
