简体繁体 English

在svn上提交之前检查每个提交

[英]Check each commit before it's commited on svn

原文 2013-05-27 13:18:32 4 1 svn/ commit

I have a quite big project and i want to give some of the work to an indian company. 我有一个很大的项目，我想把一些工作交给一家印度公司。

The project is hosted on a SVN Server, I want that one of my employees checks each commit of the extern developers and valid ( or not ) the changes ( valid = push the commit to our svn repository ). 该项目托管在SVN服务器上，我希望我的一名员工检查extern开发人员的每次提交并确认（或不更改）更改（有效=将提交推送到我们的svn存储库）。 I want that the extern developers can always do Update to get the most updated version. 我希望外部开发人员可以始终执行Update以获得最新版本。

Do you know how can i achieve this ? 你知道我该怎么做到吗？

I taught, for my employee, to have an svn folder where Update comes from a url ( svn for externs ) , and commit goes to another url ( our svn ). 我为我的员工教了一个svn文件夹，其中Update来自一个URL（svn代表externs），然后提交到另一个URL（我们的svn）。

And for the externs, a folder which does Update from our svn server, and commit to their svn. 对于externs，是一个从svn服务器执行Update并将其提交到svn的文件夹。

Well it seems complicated ( maybe impossible ), has someone did this already? 好吧，这似乎很复杂（也许不可能），有人已经这样做了吗？

1 个解决方案

A native way to it is with two branches. 本机的方法是有两个分支。 Let name it branch_development and branch_final . 让我们将其命名为branch_development和branch_final 。 All development goes to branch_development and the reviewed commits will be merged to branch_final (use tortoiseSVN or something like this). 所有开发都转到branch_development ，审阅的提交将合并到branch_final （使用tortoiseSVN或类似的东西）。 But be aware if you omit/revise to many commits it will lead you to merge conflicts (technical and logical). 但是请注意，如果您忽略/修订了许多提交，将导致您合并冲突（技术性和逻辑性）。