我最终在托管的裸存储库上操作。看起来filter-repo是要在一个仓库的干净克隆上使用的：

git filter-repo --strip-blobs-bigger-than 4M
Aborting: Refusing to destructively overwrite repo history since
this does not look like a fresh clone.
  (expected freshly packed repo)
Please operate on a fresh clone instead.  If you want to proceed
anyway, use --force.

所以我在一个干净的克隆上重试，指令运行了，但后来我对下一步该怎么做一无所知。不存在要提交或推送的文件更改本身，“Meta数据”被修改。有趣的是，该操作还从.git/config中剥离了[remote "origin"]和[branch "master"]，因此我需要重新建立远程和分支。
所以我决定继续修改托管的裸存储库。该工具识别出它不是一个干净的克隆：

warning: no corresponding .pack: ./objects/pack/pack-f8fc2556f0b95c1a66219fe3ad3fe41d6319a985.idx
Aborting: Refusing to destructively overwrite repo history since
this does not look like a fresh clone.
  (expected freshly packed repo)
Please operate on a fresh clone instead.  If you want to proceed
anyway, use --force.

通过强制，Meta数据大小从1.3GB减少到150 MB，与在干净克隆元数据上执行类似。

> git filter-repo --force --strip-blobs-bigger-than 4M
Processed 19965 blob sizes
Parsed 3536 commits
New history written in 1.44 seconds; now repacking/cleaning...
Repacking your repo and cleaning out old unneeded objects
Enumerating objects: 42458, done.
Counting objects: 100% (42458/42458), done.
Delta compression using up to 8 threads
Compressing objects: 100% (12993/12993), done.
Writing objects: 100% (42458/42458), done.
Selecting bitmap commits: 3257, done.
Building bitmaps: 100% (137/137), done.
Total 42458 (delta 33284), reused 37896 (delta 29067), pack-reused 0
Removing duplicate objects: 100% (256/256), done.
Completely finished after 10.20 seconds.

这恰好是一个Windows环境，在那之后我开始了一个干净的克隆，我不得不重新信任Visual Studio中的存储库。到目前为止，我可以推动一些变化，我会报告回来，如果有什么似乎不工作。
如果你正在处理由GitHub或其他git服务管理的存储库，那就是另一回事了，在这种情况下，你将无法直接访问他们管理的裸存储库。不知道在这种情况下会发生什么。我想你可以以某种方式推动Meta数据的变化？应该有人评论。