Re: pre-commit hook newbie: enforcing ChangeLog updates

A very useful trick is to require a bug track key... for us it is a
JIRA key like 'SAK-xxxx' and FAIL in a pre-commit if it is absent....
*or* if the much-discouraged 'NOJIRA' flag is absent in the comment.

We use this to build change logs by parsing the xml output from svn
log --xml for these keys and spitting out Confluence wiki markup

You can see an example from our last vendor drop here:
https://confluence.ucdavis.edu/confluence/x/jAGq

On Fri, Aug 22, 2008 at 10:52 AM, Janek Kozicki <janek_listy_at_wp.pl> wrote:
> Ryan Schmidt said: (by the date of Fri, 22 Aug 2008 12:16:36 -0500)
>
>> If you just want to keep track of what others in your team are
>> committing -- and that's a good thing to be keeping track of -- it's
>> useful to set up a commit mailing list, to which an automated email
>> is sent after every commit, with the diff of the commit. This way
>> changes can be reviewed and critiqued immediately.
>
> yes, we already have that. Useful for grepping diffs also. But not
> enough :) The code is too big. A short summary in a ChangeLog will be
> more useful.
>
> --
> Janek Kozicki |
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>

-- 
Jon Gorrono
email{>+++++++++[>+++++++++++>++++++++++++>+++++++>+++++<<<<-]>+++++++.>++++.<---.>-.+++..---.-.+.>+.<++++++.<----.+.---.>+.<++++++++.>---.>>+.<<<----.-.>++.}
http{ats.ucdavis.edu}
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org