#2427: trac-pre-commit-hook and trac-post-commit-hook should be more lenient
about
keywords.
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: jonas
Type: enhancement | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: 0.9
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by anonymous):
Well, if the trac-pre/post hooks are supposed to stand as examples, at
least they should be consistent.
The provided example of the pre-commit does not match the "behavior" of
the post-commit hook. Rather, one can use commands with the post-commit
hook that will not pass the pre-commit hook.
At the very least, the command set between the two hooks should be the
same. For example: fix, close, fixed, closed in post-commit but not
allowed in pre-commit. As well, as a tracking system with "minimal"
impact, it would be nice if the command words were as lenient as possible.
I have no argument against supporting specific ''command'' words, but for
basic functionality, it should be '''simple'''.
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2427>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
