I see . This means that some hooks mentioned recently in the list
(e.g. the pre-commit hook that aborts commits if no ticket ID is
provided in commit message) would not be supported yet via trac-admin,
isn' t it ?
JFTR, these kinds of hooks could be supported by RepositoryHookSystem
; but sometimes (e.g. SVN) a fake changeset object needs to be built
(and this means that the actual code to get this done varies from VCS
to VCS, thus justifying the structure of *different* interfaces in RHS
plugin ;o) . Moreover RHS allows to specify what actions will be
executed after triggering a particular hook.
Q:
- What about supporting this for 0.13 (at least the SVN impl
and the extension point for third party plugins ;o) ?
- 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).
- If so , what'd be the (best | right) way to actually veto
the target changeset ?
OTOH
Q:
- What's the approach considered for Mercurial plugin ?
Is it gonna be distributed with Trac core (in the future) or
is it that it will always be a separate plugin ?
PS: All these are random thoughts for >=0.13 , of course ;o)
PS: PS: I'm just a bit talkative today :P
On 5/6/10, Remy Blank <[email protected]> wrote:
> Olemis Lang wrote:
>> PS: Trac 0.12 hooks are limited to post-commit(s) ?
>
> The two hooks currently supported are post-commit (chaneset_added) and
> post-revprop-change (changeset_modififed).
>
> -- Remy
>
>
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
--
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.
