VisualSVNServerHooks.exe 有哪些可用选项？
VisualSVN Server 提供了一个名为 VisualSVNServerHooks 的 exe，它具有一些命令行可配置挂钩，但据我所知，只有一个用于检查文件名大小写敏感性的预提交和一个用于发送电子邮件通知的后提交。 这似乎有点浪费了机会； 有谁知道该工具是否支持任何其他挂钩？ 当然甚至是基本的强制消息挂钩？ 显然，您仍然可以独立于 VisualSVN 获取挂钩脚本，但如果有开箱即用的选项，那总是很好。
VisualSVN Server provides an exe called VisualSVNServerHooks which has some command line configurable hooks but as best I can tell there's only a single pre-commit for checking the case sensitivity of file names and a single post-commit for sending an email notification. This seems like a bit of a wasted opportunity; does anyone know if there are any other hooks supported by the tool? Surely even a basic mandatory message hook? Obviously you can still source hook scripts independently of VisualSVN but it's always nice when there's an out of the box option.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这就是开箱即用的，但钩子的要点是您可以编写自己的代码来做任何您喜欢的事情。 我想最好有一些更多的“常见”功能，例如防止空日志消息、防止提交某些文件名/扩展名等。
很多钩子都是用 perl 编写的，所以我建议坚持接着就，随即。 Perl 很容易安装，获取 Strawberry Perl，然后只提取 perl.exe 和 perl.dll，如果您正在做更复杂的事情，则只需要其余部分。
您可以在 subversion 站点上找到一组常用挂钩< /a>.
That's it out-of-the-box, but the point of hooks are that you can write your own to do whatever you like. I guess it'd be nice to have a few more 'common' ones such as preventing empty log messages, preventing certain file name/extensions to be committed, etc.
A lot of hooks are written in perl, so I'd recommend sticking with that. Perl is easy to get installed, get strawberry perl, then extract just perl.exe and the perl.dll, you only need the rest of it if you're doing more complex things.
You can find a set of common hooks on the subversion site.
目前 VisualSVNServerHooks.exe 仅具有最流行的 Subversion 挂钩。 （您可以使用 VisualSVNServerHooks --help 命令查看所有支持的选项）
我建议您向 VisualSVN 团队发送功能请求，描述您所需的挂钩：
http://www.visualsvn.com/support/feedback
Currently VisualSVNServerHooks.exe has only most popular Subversion hooks. (You can see all supported options using VisualSVNServerHooks --help command)
I recommend you to send feature request to VisualSVN Team describing of hooks that you needed:
http://www.visualsvn.com/support/feedback