Our company uses (and supports!) SVN, but I prefer to use git. What I want to try is to have a git repository - one per project, the project developers will be able to extract from this repository (and, of course, pull them apart if they want). But I still want to make all the changes to SVN, because SVN is supported by our technical support.
I tested the script with the following repositories:
- SVN repository - this is maintained by our company, and our team must make all changes there at any time.
- git-svn-clone is the git repository cloned from SVN above - all project developers should click on their commits here
- git-dev-clone is a git repository.
The only problem with the direct use of "git svn rebase" and "git svn dcommit" that I noticed is that after each click from the git developer repository to the git-svn-clone repository I need to reinstall the developer repository as soon as the changes are distributed on SVN and reinstalled. What I want to achieve is to avoid a reboot after every click.
Please note that I assume that every project developer will use only the git repository, and no one will use SVN directly.
I was able to perform this behavior manually by checking each git commit one at a time in the git-svn-clone 'repository after pushing and committing these changes to the SVN using the SVN client. I suppose git svn dcommit does the same, but also syncs with SVN and changes the commit of the SHA identifiers, which forces me to reinstall.
PS function: --no-rebase for git svn dcommit did not help, because after the first transfer passed to git svn dcommit did not allow me to make more changes to SVN until the previous one was reinstalled. I tried this behavior once and probably could have missed something.
git rebase svn git-svn
Snowbear
source share