Two Step Commit with SVN, Git,

Question

I would like to set up a version control system in which developers can push/commit they changes to one repository. Our testing department can pull those changes and test them. After those changes have been approved by the testing department, they would be committed to a second repository, ready for release.

I know we could use branches for this, but there are a lots of micro-changes and creating a branch for each of them seems like an overhead to me.

So in short, I need a system where each commit acts like a branch and can be individually merged to a master repository.

Note: Git's index does not count, since it exists only locally and can not be accessed by the testing department.

Answer 1

With a distributed repo like Git, you don't need branches, you need multiple repos, one acting as a gatekeeper from the other.

Whenever you push to the gatekeeper repo, that repo triggers through a post-receive hook the tests.
If those tests pass, it pushed to the final repo which acts as the blessed referential for all developers to pull from.

This does not test "by commit", but for each set of commits pushed.

I mentioned that before when the final repo was actually an svn one .
I also mentioned it for tests or for private builds .