问题描述
我想防止开发人员直接在主干上工作.
I'd like to prevent developers working directly on the trunk.
我的目标是强制所有开发人员脱离主干，并在自己的分支机构上工作，直到清除CI测试为止.然后，他们必须从主干合并到分支(以获取最新更改)，然后运行并通过测试，然后再合并回主干.
I'm aiming to enforce all developers off the trunk and to work on there own branches until CI tests are cleared. They then have to merge from the trunk to their branch (to pick up latest changes), run and pass tests before they merge back to the trunk.
使用这种样式的SVN是否有任何规则?
Is there any rules for this style of SVN usage?
推荐答案
限制干线提交给机器人.该机器人可以进行无冲突的合并并提交到中继.我已经做到了；它称为 mergebot (麻省理工学院许可).它是一个守护程序和一个Trac插件，提供了一种按门票分配分支的方法.文档很薄，在极端情况下会出现问题，但大多数情况下都可以正常工作.
Limit trunk commits to a bot. That bot can do the conflict-free merge and commit to trunk. I've done just that; it's called mergebot (MIT licensed). It's a daemon and a Trac plugin to provide a way to have a branch per-ticket. Docs are thin, there are issues in corner cases, but it mostly just works.
这篇关于除了分支合并以外，如何锁定SVN中继?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！