清理Git仓库冗余Subtree引用：解决误操作致仓库过大问题

Got it, let's work through this problem—those stray subtree references and leftover commit objects are definitely the culprit behind your repo's ballooned size, even after you removed the actual subtree code. Here's a step-by-step approach to clean things up safely:

1. Remove the Leftover Remote Reference #

First, let's make sure we've fully gotten rid of the rogue remote you added:

• Check all existing remotes with:

  git remote -v
  

• If you still see somename listed, delete it immediately:

  git remote remove somename
  

2. Rewrite History to Erase Subtree Commit Traces #

The real issue is that those squashed subtree commits are still lurking in your Git object database. We'll use git filter-repo (the modern, safer replacement for git filter-branch) to scrub them out:

Critical Note: Before doing this, make a full backup of your local repo folder—rewriting history is destructive, and you'll want a fallback if something goes wrong.

• If you remember the subtree prefix (ui in your case), run this to remove all traces of that path from your entire history:

  git filter-repo --path ui --invert-paths
  

• Alternatively, if you can find the exact commit hashes of the problematic subtree adds, target them directly:

  git filter-repo --remove-commits <bad-commit-hash-1> <bad-commit-hash-2>
  

  You can locate these commits with:

  git log --all --grep="subtree add"
  

3. Purge Unreferenced Git Objects #

Now that we've rewritten history, let's force Git to clean up all the orphaned objects that were taking up space:

git reflog expire --expire=now --all
git gc --prune=now --aggressive

4. Update the Remote Repo #

Since we've rewritten your local history, you'll need to force-push the cleaned-up version to your remote. Warning: This will overwrite the remote history—make sure your team knows about this so they don't push conflicting changes:

git push origin --force --all
# If you have tags that need cleaning too:
git push origin --force --tags

For Your Team Members #

Anyone with a local copy of the repo will need to discard their old history and fetch the cleaned version:

git fetch origin
git reset --hard origin/<their-working-branch>

That should strip out all the leftover subtree cruft and get your repo size back down to where it should be.

内容的提问来源于stack exchange，提问作者frederickd