On Thu, May 6, 2010 at 3:24 PM, Remy Blank <[email protected]> wrote: > Olemis Lang wrote: >> [...] >> - What about adding a hook parameter to trac-admin >> command ? I mean, with Mercurial and DVCS, similar >> hooks might be invoked on different similar events (i.e. >> not all for all events). > > I don't understand what you mean... >
E.g. Mercurial has >> - If so , what'd be the (best | right) way to actually veto >> the target changeset ? > > Your example of vetoing a changeset that doesn't refer to a ticket > actually doesn't have anything to do with a Trac repository hook. What > you need is to extract any ticket references from the commit message, > something you can do with a regexp, and to check if that ticket exists. > For this, a `trac-admin $ENV ticket list` command would be useful > (possibly with an optional query), but you could also just use a SQL query. > Well , the idea was to implement this as a Trac plugin similar to CommitTicketUpdater (more precisely RHS equivalent) but triggered on pre-commit activation ;o) . However , the . The (my) intention is to implement (all ?) kinds of hooks as Trac plugins and manage them inside Trac GUI (e.g. using admin panels ;o) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: Hessian: Initial working implementation - http://simelo.hg.sourceforge.net/hgweb/simelo/trac-rpcext/rev/ad5774008134 -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
