This post is a copy from Matthias Schoettle’s blog
Let us just moved one directory within a Git repository to a directory within another repository including its history. For example:
repositoryA/
```console
.........../directoryToKeep
.........../otherDirectory
.........../someFile.ext
repositoryB/
.........../someStuff
The goal is to move directoryToKeep into repositoryB with its history, i.e., all commits that affect directory1. If instead, you want to create a repository just for the contents of directoryToKeep, just skip the last step of the preparation of the source repository.
A. Prepare the source repository
- Clone repositoryA (make a copy, don’t use your already existing one)
cdto it- Delete the link to the original repository to avoid accidentally making any remote changes
git remote rm origin -
Using
filter-branch, go through the complete history and remove all commits (or keep all commits affectingdirectoryToKeep) not related todirectoryToKeep.git filter-branch --subdirectory-filter <directoryToKeep> -- --allFrom the git documenta
Only look at the history which touches the given subdirectory. The result will contain that directory (and only that) as its project root.
You might need to add
--prune-emptyto avoid empty commits, in my case it was not necessary.
This means that the result will berepositoryAcontaining the contents ofdirectoryToKeepdirectly, which is also reflected in all the commits. If you want to create a separate repository just fordirectoryToKeep, skip the next step. If instead you want to movedirectoryToKeeptorepositoryBinto its own directory, you basically have two options. You might be fine with the way the commits are and create an additional commit that moves all files into a directory. However, if you are a perfectionist like myself, you can perform the following command to movedirectoryToKeepinto its own directory, which will update all remaining commits accordingly. - Replace
directoryToKeepwith your actual directory before, and execute the following command using index-filter this time:git filter-branch --index-filter ' git ls-files -sz | perl -0pe "s{\t}{\tdirectoryToKeep/}" | GIT_INDEX_FILE=$GIT_INDEX_FILE.new \ git update-index --clear -z --index-info && mv "$GIT_INDEX_FILE.new" "$GIT_INDEX_FILE" ' HEADIf you want to preserve tags and update them, you need to add –tag-name-filter cat.
There might be old untracked files. You can clean up the repository with the following commands:
git reset --hard
git gc --aggressive
git prune
git clean -df
If you just want a new repository for directoryToKeep, you should be able to just push it. Otherwise follow the second step.
It’s also good at this point to make sure that the result is correct, e.g., using git log.
B. Merge into target repository
- Clone repository (make a copy, don’t use your already existing one)
cdinto it- Create a remote connection to
repositoryAas a branch inrepositoryB.git remote add <branch-name-repoA> /path/to/repositoryA - Pull from the branch (this assumes you performed the changes above on master)
git pull --allow-unrelated-histories <branch-name-repoA> masterNote: Because your branch and master don’t have a common base, git 2.9+ will refuse to merge them without the
--allow-unrelated-historiesoption. It will create a merge commit to merge the currentHEADwith your branch. The editor for the commit message should appear. Enter a meaningful commit message and proceed. Now you’re done and can push.
