I have multiple projects hosted OnDemand, A and B - each with their own subversion repository.
A has an svn:externals to B, such that checking out A gives
As part of the migration to GIT on bitbucket I would like to combine the two subversion repositories into a single git repository (A.git), such that checing out A.git would give the same layout as svn gave.
Since we no longer need to check out B on its own, I don't see the reason to propagate the modules approach.
I need each SVN commit to remain as an identifiable single git commit.
What solution does Atlassian recommend ?
I wouldn't go so far as to call this the Atlassian recommended approach, but I'll try to answer your question.
The git way that roughly (but with some drawbacks) maps to using svn:externals would be submodules (http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html). Submodules allow you to have one Git repository as a subdirectory of another Git repository with separate commit histories. You clearly stated that checking out B is not longer required and that you don't want/need to propagate the module approach so git submodules are not necessarily required.
One option that retains the history of commits is the subtree command that is available in git/contrib:
Note: git installed via Homebrew on Mac OS X installs the `subtree` command automatically, otherwise you'd need to follow the installation instructions on https://github.com/git/git/blob/master/contrib/subtree/INSTALL.
This needs to be done for the creation of the merged history only. After pushing the changes, other git clients will get the merged history without requiring this subcommand to be available. Further down I show how the same result can be achieved without having to install the subtree command.
This example will merge two git repositories into one, with the second ending up in a subdirectory of the first:
$> git clone firstname.lastname@example.org:ssaasen/git-pastiche.git Cloning into 'git-pastiche'... $> cd git-pastiche $> ls -l total 24 -rw-r--r-- 1 ssaasen staff 815 9 Feb 12:34 Makefile -rw-r--r-- 1 ssaasen staff 1269 9 Feb 12:34 README.md drwxr-xr-x 10 ssaasen staff 340 9 Feb 12:34 bin -rw-r--r-- 1 ssaasen staff 1214 9 Feb 12:34 build.hs drwxr-xr-x 10 ssaasen staff 340 9 Feb 12:34 man $> git remote add spy -f email@example.com:ssaasen/spy.git warning: no common commits remote: Counting objects: 231, done. remote: Compressing objects: 100% (20 ... $> git subtree add --prefix=spy spy/master Added dir 'spy' $> ls -l total 24 -rw-r--r-- 1 ssaasen staff 815 9 Feb 12:34 Makefile -rw-r--r-- 1 ssaasen staff 1269 9 Feb 12:34 README.md drwxr-xr-x 10 ssaasen staff 340 9 Feb 12:34 bin -rw-r--r-- 1 ssaasen staff 1214 9 Feb 12:34 build.hs drwxr-xr-x 10 ssaasen staff 340 9 Feb 12:34 man drwxr-xr-x 13 ssaasen staff 442 9 Feb 12:35 spy <=====
This will add the project firstname.lastname@example.org:ssaasen/spy.git in the subdirectory ./spy with its history retained:
Pushing this combined repository to its new location will make the combined history available in a single repository.
There are a few caveats though:
If it's important to be able to not only reference the commits of the merged repository but branches and tags for each, git submodules might be a better option for your use case even though you wanted to move away from a module approach.
The same result can be achieved using subtree merging directly without the need for the subtree command to be installed:
$> git clone email@example.com:ssaasen/git-pastiche.git $> cd git-pastiche/ $> git remote add spy -f firstname.lastname@example.org:ssaasen/spy.git $> git merge -s ours --no-commit spy/master $> git read-tree --prefix=spy -u spy/master $> git commit -m "Add ./spy as a subtree merging email@example.com:ssaasen/spy.git"
Hope this helps.
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot