Page History

Freaky Git stuff

Nigel Stanger edited this page 14 days ago

Clone this wiki locally


To migrate a large repository to LFS in GitBucket:

  1. Create a new repository newrepo on the server by cloning the old one.
  2. Clone newrepo to local.
  3. Initialise git-lfs in newrepo as per the git-lfs tutorial:
    git lfs track "*.thing1" "*.thing2"
    git add .gitattributes
    git commit -m "Track thing1, thing2 files (LFS)"
    git rm --cached "*.thing1" "*.thing2"
    git add .
    git commit -m "Convert last commit to LFS"
  4. Migrate the history as per the git-lfs tutorial:
    git lfs migrate import --everything --include="*.thing1,*.thing2"
    If you specify multiple --include switches only the last one will take effect, so to migrate multiple file types, put the glob expressions inside the same string as shown above.
  5. We now need to force push newrepo to remote, but it may be too large for nginx’s request size limits. If you happen to have release tags handily scattered throughout history (or you can identify some well-spaced commit hashes) you can reduce the request size by only pushing up to a certain commit, e.g.:
    git push --force origin 9d42ad26508d94429ce2179358db5c2bfc1dc03d:master
    # ...etc...
    # one last push to catch everything since the last tag:
    git push --force
    Do this for each of the tags/commits in chronological order. You can find the commit hashes for the tags using git show-ref --tags.
  6. Also force push the rewritten tags to prevent push/pull errors due to the different commit hashes:
    git push --force --tags
  7. Clean up local as per the git-lfs tutorial:
    git reflog expire --expire-unreachable=now --all
    git gc --prune=now

Finding repositories that haven’t been pushed

Something along these lines (from comments on

find . -name .git -type d -print -exec git --git-dir={} --work-tree={}/.. cherry -v \;