在GitHub上检查你上次提交的id 然后用这个

Git reset——soft <commit_id>

我想是因为工作。谢谢

我尝试了以上所有的方法，但没有一个对我有效。

然后我想出了自己的解决办法。

First of all, you need a clean, up-to-date local repo. Delete all the large files. Now create a new folder OUTSIDE of your repo folder and use "Git create repository here" to make it a new Git repository, let's call it new_local_repo. This is it! All above methods said you have to clean the history..., well, I'm sick of that, let's create a new repo which has no history at all! Copy the files from your old, messed up local repo to the new, beautiful repo. Note that the green logo on the folder icon will disappear, this is promising because this is a new repo! Commit to the local branch and then push to remote new branch. Let's call it new_remote_branch. If you don't know how to push from a new local repo, Google it. Congrats! You have pushed your clean, up-to-date code to GitHub. If you don't need the remote master branch anymore, you can make your new_remote_branch as new master branch. If you don't know how to do it, Google it. Last step, it's time to delete the messed up old local repo. In the future you only use the new_local_repo.

如果你在寻求帮助之前就已经把你的回购搞得一团糟，我发现这里有一些非常有用的东西。第一类型:

git status

在此之后，您应该会看到类似于

On branch master
Your branch is ahead of 'origin/master' by 2 commits.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean

重要的部分是“2次提交”!从这里，继续输入:

git reset HEAD~<HOWEVER MANY COMMITS YOU WERE BEHIND>

所以，对于上面的例子，你可以输入:

git reset HEAD~2

在你输入之后，你的“git状态”应该是:

On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean

从那里，您可以删除大文件(假设您还没有这样做)，并且您应该能够重新提交所有内容而不会丢失您的工作。

如果这个文件是你最近一次提交时添加的，而且你还没有推送到远程存储库，你可以删除这个文件并修改提交。

git rm --cached giant_file
    # Stage "giant_file" for removal with "git rm"
    # Leave it on disk with "--cached". if you want to remove it from disk
    # then ignore the "--cached" parameter
git commit --amend -CHEAD
    # Commit the current tree without the giant file using "git commit"
    # Amend the previous commit with your change "--amend" 
    # (simply making a new commit won't work, as you need
    # to remove the file from the unpushed history as well)
    # Use the log/authorship/timestamp of the last commit (the one we are
    # amending) with "-CHEAD", equivalent to --reuse-message=HEAD
git push
    # Push our rewritten, smaller commit with "git push"

我遇到了类似的问题，并使用上面的步骤删除文件。它工作得很完美。

然后我得到了一个错误的第二个文件，我需要删除: remote: error: File <path/filename> is 109.99 MB;这超过了GitHub的文件大小限制100.00 MB

我尝试了相同的步骤，得到一个错误:“以前的备份已经存在于<path/filename>”

从这个网站上的研究，我使用命令:git filter-branch——force——index-filter "git rm——cached——ignore-unmatch <path/filename>"——prune-empty——tag-name-filter cat -- --all

工作很好，大文件被删除了。

令人难以置信的是，推送仍然失败了，并出现了另一个错误:curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104 fatal:远端异常挂起

我通过直接修改.git配置文件- postBuffer = 999999999来修复这个问题

在那之后，推力通过了!

我发现压缩比过滤分支更有用。我做了以下事情:

本地删除大文件。 提交本地删除。 软重置回X次提交(对我来说是3):git重置-软头~3。 然后重新提交所有的更改(AKA squash) git commit -m "合并提交的新消息" 推送压缩提交。

特殊情况(来自用户@lituo):如果上述情况不起作用，那么您可能会遇到这种情况。提交1包含大文件，由于大文件错误，提交1的推送失败。提交2删除了git rm——cached [file_name]的大文件，但提交2的推送仍然失败。您可以遵循上面相同的步骤，但不要使用HEAD~3，而是使用HEAD~2。