Share common / useful SVN pre-commit hooks [closed]

Answer 1

I use a post-commit hook to rewrite the author property to a friendly name from our ldap tree. (authentication is with employee id)

Answer 2

Insert a note into Mantis bugtracker with the changelist details based on the commit message having 'issue #' or the like via RegEx.

Answer 3

I like using svn hooks to:

• enforce the stricter points of code style
• check for obvious syntax errors
• make sure special Trac keywords like "Fixes" or "Addresses" are actually preceding the appropriate issue number

Answer 4

That it has a commit message, and it is != than "bug fixing". Damn, did I hate those useless messages!

Answer 5

I do a word count on submit messages. They need to be 5 words or more. This has led to some comedic insults against me...

Answer 6

In the company I currently work on, this is checked:

• If binary files have the needs lock attribute set;
• If the Java files have the standard copyright notice and if it includes the current year;
• If the code is properly formatted (we use Jalopy for code formatting) - this may sound silly but it actually makes text comparisons between different versions easier;
• If the code has a commit message;
• If the directory structure conforms to what is defined (all projects should be under a defined SVN folder, and each project should have a tags, branch and trunk folder);

I guess that's it.

I like the idea of checking if the commit is associated with a ticket; it actually makes a lot of sense to me.