Option to force users to enter a comment when committing changes
We believe this needs to be setup on your source control system and not on the SQL Source Control client.
For SVN users, configure a pre-commit hook to require comments.
For TFS users, this would be done through a policy, but we currently ignore these. If this is something you would like, please vote/comment at http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/726952-evaluate-tfs-policies-when-committing-db-changes.
Thank you!
Stephanie Herr :-)
SQL Source Control Project Manager
-
Patrick Ortuso commented
Hi, since the last couple of version upgrade, we do not have a choice when linking a DB to our GIT source control. Now we *MUST* do a commit and not just a save. We have, in our GIT, the mandatory commit message control set, but because we cannot set Redgate to require a manadory commit message, it generates an error. Could you please reopen this case and reevaluated with th current Redgate version?
-
Your Subversion administrator should be able to set up a pre-commit hook, which will force users to enter comments. If your Subvesrion is set up to require comments, then SQL Source Control will require you to have comments. More info - http://www.svnforum.org/2017/viewtopic.php?t=1212.
-
AdminPeter_Peart (Admin, Redgate) commented
Hi there,
As far as I am aware, you can control this from your Source Control system. If your system does not permit empty commit messages, the commit to the system using SQL Source Control will fail with an error message saying something like "you need to comment on this".
If therefore you ensure that comments have to be made upon commits, this should then filter through to SQL Source Control.
Pete