Require comments PRE-commit
I understand a hook can be added to SVN so if a commit is made without a comment it will throw an error and fail - From an interface point of view it would be nice the commit couldn't even be made (i.e. the button was disabled if a "require comments" option was set).
Matthew Ryba commented
I agree it would be great if there was an option in the RedGate_SQLSourceControl_CommonUI_UIOptions.xml file that would require comments on commit regardless of what repo (TFS, GIT) is being used. This would allow an organization to determine how the commits are handled and not force them to use one system of source control over another.
CJ Butcher commented
Yes! This is a MUST. Checking something in without a comment should be considered a sin, allowing it to happen is aiding and abetting. Being allowed to click the commit button, watching everything get processed to then get a message saying you haven't met the requirements is not the right direction.
@Paul - You can configure SVN using commit hooks. If you do a web search you should be able to find out how to do this. One solution I found is here: http://stackoverflow.com/questions/1928023/how-can-i-prevent-subversion-commits-without-comments
We use SVN and a feature like this would be handy. We would also want to require the committer to enter their initials or name or...
Having optional required fields would be handy. Especially if things like initials were appended automatically for the developer.
Thanks for the suggestion. Which source control system are you using?
Karthik P commented
When committing changes to source control, Developer should enter the comments(This is our rule) for that I need to set the Comments as mandatory.
Now SQL Source control not have any feature to set the comments as mandatory.