(The common practice is to not store the entire history of the subproject in your main repository, but If you want to preserve it just omit the –squash flag. vim/bundle/tpope-vim-surround main -squash First add git subtree at a specified prefix folder: git subtree add -prefix. If you just want a couple of one-liners to cut and paste, read this paragraph. The quick and dirty way without remote tracking Here is a canonical example of tracking a vim plug-in using git subtree. If your repository is large, this option might make your build pipeline more efficient. Effectively this results in git fetch -depthn. The version installed by homebrew on OSX already has subtree properly wired, but on some platforms you might need to follow the installation instructions. Select if you want to limit how far back in history to download. Git subtree is available in stock version of Git since May 2012 – v1.7.11 and above. The responsibility of not mixing super and sub-project code in commits lies with you.Contributing code back upstream for the sub-projects is slightly more complicated.You must learn about a new merge strategy (i.e.Contents of the module can be modified without having a separate repository copy of the dependency somewhere else.ĭrawbacks (but in our opinion they're largely acceptable):. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |