On Wednesday, January 14, 2015 at 12:14:25 AM UTC-8, Riedel, Torge wrote: > > Hi, > > > > we use TicketChangeLogPlugin here in several instances. Since now we were > limited in our commit messages to the format supported by default > log_pattern. > > I played around with an online regex-tool to support all (I hope) commit > messages containing a reference to the ticket. The result is: > > > > [ticketlog] > > log_pattern = (\n|.)*#%s($|\D(\n|.)*) > > > > Explanation: > > 1. Allow zero or more characters before the ticket id (including > newline characters) > > 2. Allow zero or more characters after the ticket id (including > newline characters), but if there are characters after the ticket id, the > first must not be a digit (0..9). Which avoids listing ticket references to > e.g. ticket #40 in ticket #4. > > > > Feel free to document this log pattern on the wiki page of > TicketChangeLogPlugin > > > > Regards > > Torge > > Since it's related I'll mention that in #11821 (1) I proposed to utilize the patterns from Trac's CommitTicketUpdater (2). I think it would be good to use the more familiar patterns in TicketChangeLogPlugin.
(1) http://trac-hacks.org/ticket/11821 (2) http://trac.edgewall.org/wiki/CommitTicketUpdater#Configure -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
