If you hate
git submodule, then you may want to give
git subtree a try.
Let's say you have a git repository
init'd with at least one commit.
You can add another repository to this respository like this:
In other words
- First specify you want to add the subtree
- Then specify the prefix directory into which you want to pull
- Specify the remote repository
- Specify the remote branch
- Specify you want to squash all the remote repository's logs
git subtree add --prefix .vimrepo https://github.com/newfivefour/vimrc.git master --squash
This will clone
https://github.com/newfivefour/vimrc.git into the directory
If you want to pull in any new commits to the subtree from the remote, issue the same command as above, replacing
git subtree pull --prefix .vimrepo https://github.com/newfivefour/vimrc.git master --squash
If you make a change to anything in
.vimrepo the commit will be stored in the host repository and its logs.
That is the biggest change from submodules.
If you now want to update the subtree repository with that commit, you must run the came command as above, excluding
--squash and replacing
git subtree push --prefix .vimrepo https://github.com/newfivefour/vimrc.git master
I've only just starting playing, but my main problems so far:
Other than that, they're looking nicer than submodules.
- You can't easily list the subtrees in your project
- You can't, at least easily, list the remote repositories of the subtrees
- The logs are slightly confusing when you update the host repository with subtree commits, then push the subtree to its host, and then pull the subtree.
Page 1 of 1