[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Request for more hooks

From: Andrew Simpson <tsvn-357654_at_simpsonite.com>
Date: Thu, 12 Mar 2009 04:37:00 -0700 (PDT)

Hi,

Our project is trying to implement a mechanism to automate various build-related tasks (e.g. assigning version numbers, ensuring different build items are compatible, generating release notes, etc.) In order to help generate release notes and keep track of dependencies, we are trying to enforce a standard template for each commit message.

The enforcement can be done easily enough at the server, but we would like TortoiseSVN to generate the template for us. For a normal commit, we've successfully done this using a start-commit hook. However, when branching, tagging, or using any other operation that requires a message (e.g. copying or deleting via the repo-browser), the script is not executed.

So, the request is for a hook to be executed whenever a message is asked for, so that the template can be inserted. It would be nice if this was a single hook that was called for any message, possibly with an action code (e.g. commit, copy, delete, etc.) This would be easier for users to set up than having one script per action.

On a similar subject, having merge hooks would also help us track merges - the current merge tracking mechanism isn't sufficient for our needs, and users sometimes don't put enough information in the commit message to indicate what was merged. A hook would allow us to capture this information, and the message hook could insert the correct merge comment.

Regards,
Andrew

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=1312468

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-12 12:38:11 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.