它看起来是这样的:

git rm --cached /config/deploy.rb
echo /config/deploy.rb >> .gitignore

从git中删除跟踪文件的缓存，并将该文件添加到.gitignore列表中

Git filter-repo现在正式推荐超过Git filter-branch

在git 2.5本身的git filter-branch的手册中提到了这一点。

从git/GitHub的历史记录中删除文件夹及其内容

pip install git-filter-repo
git filter-repo --path path/to/remove1 --path path/to/remove2 --invert-paths

这将自动删除空提交。

或者你可以替换某些字符串:如何替换整个Git历史中的字符串?

git filter-repo --replace-text <(echo 'my_password==>xxxxxxxx')

如果您推送到GitHub，强制推送不够，请删除存储库或联系技术支持

即使你在一秒钟后强行推，这也不够，如下所述。

唯一有效的做法是:

泄露的是像密码一样可更改的凭证吗? 是:立即修改您的密码，并考虑使用更多的OAuth和API密钥! 不(裸照): 您是否关心存储库中的所有问题都被nuked? No:删除存储库 是的: 联络支持 如果泄漏对你来说非常重要，以至于你愿意让一些存储库停机以降低泄漏的可能性，那么在你等待GitHub支持回复你的时候，将其设置为私有

一秒钟后的推力是不够的，因为:

GitHub keeps dangling commits for a long time. GitHub staff does have the power to delete such dangling commits if you contact them however. I experienced this first hand when I uploaded all GitHub commit emails to a repo they asked me to take it down, so I did, and they did a gc. Pull requests that contain the data have to be deleted however: that repo data remained accessible up to one year after initial takedown due to this. Dangling commits can be seen either through: the commit web UI: https://github.com/cirosantilli/test-dangling/commit/53df36c09f092bbb59f2faa34eba15cd89ef8e83 (Wayback machine) the API: https://api.github.com/repos/cirosantilli/test-dangling/commits/53df36c09f092bbb59f2faa34eba15cd89ef8e83 (Wayback machine) One convenient way to get the source at that commit then is to use the download zip method, which can accept any reference, e.g.: https://github.com/cirosantilli/myrepo/archive/SHA.zip It is possible to fetch the missing SHAs either by: listing API events with type": "PushEvent". E.g. mine: https://api.github.com/users/cirosantilli/events/public (Wayback machine) more conveniently sometimes, by looking at the SHAs of pull requests that attempted to remove the content There are scrappers like http://ghtorrent.org/ and https://www.githubarchive.org/ that regularly pool GitHub data and store it elsewhere. I could not find if they scrape the actual commit diff, and that is unlikely because there would be too much data, but it is technically possible, and the NSA and friends likely have filters to archive only stuff linked to people or commits of interest.

如果你删除了存储库，而不是强制推送，提交甚至会立即从API中消失，并给出404，例如https://api.github.com/repos/cirosantilli/test-dangling-delete/commits/8c08448b5fbf0f891696819f3b2b2d653f7a3824，即使你重新创建了另一个具有相同名称的存储库，这也是有效的。

为了测试这一点，我创建了一个repo: https://github.com/cirosantilli/test-dangling，并做了:

git init
git remote add origin git@github.com:cirosantilli/test-dangling.git

touch a
git add .
git commit -m 0
git push

touch b
git add .
git commit -m 1
git push

touch c
git rm b
git add .
git commit --amend --no-edit
git push -f

参见:如何从GitHub删除悬空提交?

明确一点:公认的答案是正确的。先试试。然而，对于某些用例来说，这可能是不必要的复杂，特别是当你遇到诸如'fatal: bad revision -prune-empty'之类的讨厌错误时，或者真的不关心你的回购历史。

另一种选择是:

CD到项目的基本分支 删除敏感代码/文件 rm -rf .git/ #删除所有git信息 你的代码 去github并删除你的存储库 按照本指南将您的代码推送到一个新的存储库，就像您通常会做的那样 https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/

当然，这将删除所有提交历史分支，以及来自你的github回购和本地git回购的问题。如果这是不可接受的，你将不得不使用另一种方法。

我们可以称之为“核选项”。

它看起来是这样的:

git rm --cached /config/deploy.rb
echo /config/deploy.rb >> .gitignore

从git中删除跟踪文件的缓存，并将该文件添加到.gitignore列表中

这是我在windows下的解决方案

git filter-branch——tree-filter "rm -f 'filedir/filename' Git push—force

确保路径正确 否则行不通

我希望这对你们有帮助

使用filter-branch:

git filter-branch --force --index-filter 'git rm --cached --ignore-unmatch *file_path_relative_to_git_repo*' --prune-empty --tag-name-filter cat -- --all

git push origin *branch_name* -f