Quantcast
Channel: SVNForum.org - Subversion Forum - Windows Servers
Viewing all articles
Browse latest Browse all 74

Best practices-Enforcing that every commit contains log message and svn:keywords $Id

$
0
0
I'm responsible for a repo and need to enforce that every commit includes a log message and that every item being committed has the $Id svn:keywords property set. Failure of either should reject the commit.

I found the template samples, and I'm pretty sure i can enforce the log message requirement using
svnlook log -t %2 %1 | findstr /R "[a-zA-Z0-9]" and examine ERRORLEVEL after to determine whether a log message of at least one character was provided.

I realize this isn't much of a step forward, but the heart of my question has to do with the second problem. If a single commit is going to Add files/directories, and/or modify files, how might I confirm that every file being committed has it's svn:keywords property set with $Id?

AdThanksVance,

Murad

Viewing all articles
Browse latest Browse all 74

Trending Articles