github 上犯了个低级错误，怎么补救

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

现在注册

已注册用户请登录

• 请不要在回答技术问题时复制粘贴 AI 生成的内容

项目里，fork 了一个项目，弄完了心想回馈一下作者，就从我的私有 gitlab 里 push 到 github ，然后点了一下 pull request

但是忘了 squash commit ，中间版本还能看到我的.gitlab-ci.yml

这玩意还删不掉，只能 close pull request

好在敏感信息都是变量，里面就一个私有的 docker 镜像地址。

第 1 条附言 · 19 小时 34 分钟前

后续：发工单解决问题了

GitHub

pull request

squash commit

13 条回复 • 2025-11-20 15:40:13 +08:00

CodeCaster

1 天前

强制推送覆盖可以解决么？

Shorekeeper

1 天前

https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/removing-sensitive-data-from-a-repository#fully-removing-the-data-from-github

Contact us through the GitHub Support portal, and provide the following information:

The owner and repository name in question (e.g. YOUR-USERNAME/YOUR-REPOSITORY).
The number of affected pull requests, found in the previous step. This is used by Support to verify you understand how much will be affected.
The First Changed Commit(s) reported by git-filter-repo (Look for NOTE: First Changed Commit(s) in its output.)
If NOTE: There were LFS Objects Orphaned by this rewrite appears in the git-filter-repo output (right after the First Changed Commit), then mention you had LFS Objects Orphaned and upload the named file to the ticket as well.

If you have successfully cleaned up all references other than PRs, and no forks have references to the sensitive data, Support will then:

Dereference or delete any affected PRs on GitHub.

Run a garbage collection on the server to expunge the sensitive data from storage.

Remove cached views.

If LFS Objects are involved, delete and/or purge the orphaned LFS objects.

Important

GitHub Support won't remove non-sensitive data, and will only assist in the removal of sensitive data in cases where we determine that the risk can't be mitigated by rotating affected credentials.