entityMap|blocks|key|bqdkk|text|您可以使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6vjdf|git+filter-branch+--index-filter+'git+rm+-r+--cached+--ignore-unmatch+'+HEAD|code-block|syntax|javascript|rsaq|这将删除该文件历史记录中的所有内容。问题是该文件存在于历史记录中。|cjo91|此命令会更改提交的散列，这可能是一个真正的问题，特别是在共享存储库上。在不了解后果的情况下，不应执行此操作。^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|M|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|N|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|O|9|@]|A|@]|B|$]]]]

You can use 

<pre><code>git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch &lt;file/dir&gt;' HEAD
</code></pre>

This will delete everything in the history of that file. The problem is that the file is present in the history.

This command changes the hashes of your commits which can be a real problem, especially on shared repositories. It should not be performed without understanding the consequences.

entityMap|blocks|key|58bgc|text|如果文件是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c323a|添加了您最近的提交|3bg1g|，还有你|cea42|尚未推送到远程存储库|akf4l|，您可以删除该文件并修改提交，取自|dtp83|这里|3jiss|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"|code-block|syntax|javascript^0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|S|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|T|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|U|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|V|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|W|9|@]|A|@]|B|$]]|$2|M|4|N|6|O|8|X|9|@]|A|@]|B|$P|Q]]]]

If the file was added with your most recent commit, and you have not pushed to the remote repository, you can delete the file and amend the commit, Taken from <a href="https://help.github.com/articles/removing-files-from-a-repository-s-history/" rel="noreferrer">here</a>:

<pre><code>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"
</code></pre>

entityMap|blocks|key|fsdc1|text|我遇到了类似的问题，并使用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|ed00v|上一步|2i1v7|若要删除该文件，请执行以下操作。它工作得很完美。|2k3hr|然后，我在需要删除的第二个文件上得到了一个错误：|cqqm9|83j8n|我尝试了相同的步骤，得到一个错误：|5spog|aejnc|来自于研究|d68ca|本网站|e2pek|我使用了以下命令：|a3ols|bl7ok|效果很好，大文件被删除了。|43hac|令人难以置信的是，推送仍然失败，并出现另一个错误：|3jgih|我通过直接修改.git配置文件修复了这个问题-|34fo0|在那之后，推送通过了！^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|11|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|12|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|13|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|14|9|@]|A|@]|B|$]]|$2|I|4|-4|6|7|8|15|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|16|9|@]|A|@]|B|$]]|$2|L|4|-4|6|7|8|17|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|18|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|19|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|1A|9|@]|A|@]|B|$]]|$2|S|4|-4|6|7|8|1B|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1C|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1D|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1E|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1F|9|@]|A|@]|B|$]]]]

I had a similar issue and used the <a href="https://stackoverflow.com/a/23657759/6549295">step above</a> to remove the file. It worked perfectly. 

I then got an error on a second file that I needed to remove:
<code>remote: error: File &lt;path/filename&gt; is 109.99 MB; this exceeds GitHub's file size limit of 100.00 MB
</code>

I tried the same step, got an error: <code>"A previous backup already exists in &lt;path/filename&gt;"</code> 

From research on <a href="https://czettner.com/blog/15/07/16/deleting-big-files-git-history" rel="noreferrer">this website</a> I used the command: <code>git filter-branch --force --index-filter "git rm --cached --ignore-unmatch &lt;path/filename&gt;" --prune-empty --tag-name-filter cat -- --all</code> 

Worked great, and the large files were removed.

Unbelievably, the push still failed with another error: <code>error: RPC failed; curl 56 OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104 fatal: The remote end hung up unexpectedly</code>

This I fixed by directly modifying the .git config file - <code>postBuffer = 999999999</code>

After that the push went through!

entityMap|blocks|key|eb55f|text|我遇到了同样的问题，没有一个答案对我有效。我通过以下步骤解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c0nv4|1.查找包含大文件的提交|3e1tc|git+log+--all+--+'large_file`|code-block|syntax|javascript|eaj58|底层提交是|4fnss|最老的|dk800|在结果列表中提交。|2jpmq|2.找到最老的前面的那个。|4lrg1|git+log|28ame|假设你得到了：|efm8c|commit+3f7dd04a6e6dbdf1fff92df1f6344a06119d5d32|il00|3.+Git+rebase|nv4g|git+rebase+-i+3f7dd04a6e6dbdf1fff92df1f6344a06119d5d32|db31o|小贴士|c0v39|：|fcnht|列表项|861of|我只是选择|nmrl|因为提交包含大文件。|2al19|你可能会在改基的过程中遇到冲突，修复它们并使用|dotei|直到你完成它。|cesln|如果在rebase使用过程中出现任何错误|5hv4o|取消它。^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1J|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1K|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|1L|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|1M|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|1N|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|1O|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|1P|9|@]|A|@]|B|$]]|$2|R|4|S|6|G|8|1Q|9|@]|A|@]|B|$H|I]]|$2|T|4|U|6|7|8|1R|9|@]|A|@]|B|$]]|$2|V|4|W|6|G|8|1S|9|@]|A|@]|B|$H|I]]|$2|X|4|Y|6|7|8|1T|9|@]|A|@]|B|$]]|$2|Z|4|10|6|G|8|1U|9|@]|A|@]|B|$H|I]]|$2|11|4|12|6|7|8|1V|9|@]|A|@]|B|$]]|$2|13|4|14|6|7|8|1W|9|@]|A|@]|B|$]]|$2|15|4|16|6|7|8|1X|9|@]|A|@]|B|$]]|$2|17|4|18|6|7|8|1Y|9|@]|A|@]|B|$]]|$2|19|4|1A|6|7|8|1Z|9|@]|A|@]|B|$]]|$2|1B|4|1C|6|7|8|20|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|21|9|@]|A|@]|B|$]]|$2|1F|4|1G|6|7|8|22|9|@]|A|@]|B|$]]|$2|1H|4|1I|6|7|8|23|9|@]|A|@]|B|$]]]]

I got the same problem and none of the answers work for me. I solved by the following steps:

<h2>1. Find which commit(s) contains the large file</h2>

<pre><code>git log --all -- 'large_file`
</code></pre>

The bottom commit is the oldest commit in the result list.

<h2>2. Find the one just before the oldest.</h2>

<pre><code>git log
</code></pre>

Suppose you got: 

<pre><code>commit 3f7dd04a6e6dbdf1fff92df1f6344a06119d5d32
</code></pre>

<h2>3. Git rebase</h2>

<pre><code>git rebase -i 3f7dd04a6e6dbdf1fff92df1f6344a06119d5d32
</code></pre>

Tips: 

<ol>
<li>List item</li>
<li>I just choose <code>drop</code> for the commits contains the large file.</li>
<li>You may meet conflicts during rebase fix them and use <code>git rebase --continue</code> to continue until you finish it.</li>
<li>If anything went wrong during rebase use <code>git rebase --abort</code> to cancel it. </li>
</ol>

entityMap|blocks|key|fhbhv|text|为什么GitHub拒绝我的回购，即使我删除了大文件？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|11b33|Git存储了你项目的完整历史，所以即使你从你的项目中‘删除’了一个文件，Git+repo在它的历史中仍然有一个文件的副本，如果你试图推送到另一个存储库(比如GitHub上的一个)，那么Git|67pgq|需要|bdosr|远程存储库具有与本地存储库相同的历史记录(即其历史记录中相同的大文件)。|6lvi5|如何才能让GitHub接受我的回购？|268su|你需要在本地清理项目的Git历史，从所有历史中删除不需要的大文件，然后只使用“清理”的历史。受影响的提交的Git提交ids将更改。|2ajus|如何从我的Git存储库中清除大文件？|f1ce9|从Git历史记录中清除不需要的大文件的最佳工具是|e51b0|BFG+Repo-Cleaner|4rciu|-它是一种更简单、更快速的替代方案|a6i5u|专为从Git历史记录中删除不需要的文件而设计。|6kn1p|请仔细阅读|2rja6|使用说明|3dum8|，核心部分是这样的：|bqr42|$+java+-jar+bfg.jar+--strip-blobs-bigger-than+100M+my-repo.git|code-block|syntax|javascript|fedak|任何超过100MB的文件(不在您的|30dsh|最新版本|3s5j1|提交)将从您的Git存储库的历史记录中删除。然后，您可以使用|a9o36|要清除死数据，请执行以下操作：|eib7g|$+git+gc+--prune=now+--aggressive|8re67|BFG通常至少|ffa6a|10-50倍|ek4c7|比跑步更快|6mb7a|，而且通常使用起来要容易得多。|34oom|完全披露:我是BFG+Repo-Cleaner的作者。^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1R|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1S|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1T|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1U|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|1V|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|1W|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|1X|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|1Y|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|1Z|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|20|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|21|9|@]|A|@]|B|$]]|$2|W|4|X|6|7|8|22|9|@]|A|@]|B|$]]|$2|Y|4|Z|6|7|8|23|9|@]|A|@]|B|$]]|$2|10|4|11|6|7|8|24|9|@]|A|@]|B|$]]|$2|12|4|13|6|14|8|25|9|@]|A|@]|B|$15|16]]|$2|17|4|18|6|7|8|26|9|@]|A|@]|B|$]]|$2|19|4|1A|6|7|8|27|9|@]|A|@]|B|$]]|$2|1B|4|1C|6|7|8|28|9|@]|A|@]|B|$]]|$2|1D|4|1E|6|7|8|29|9|@]|A|@]|B|$]]|$2|1F|4|1G|6|14|8|2A|9|@]|A|@]|B|$15|16]]|$2|1H|4|1I|6|7|8|2B|9|@]|A|@]|B|$]]|$2|1J|4|1K|6|7|8|2C|9|@]|A|@]|B|$]]|$2|1L|4|1M|6|7|8|2D|9|@]|A|@]|B|$]]|$2|1N|4|1O|6|7|8|2E|9|@]|A|@]|B|$]]|$2|1P|4|1Q|6|7|8|2F|9|@]|A|@]|B|$]]]]

<h3>Why is GitHub rejecting my repo, even after I deleted the big file?</h3>

Git stores the full history of your project, so even if you 'delete' a file from your project, the Git repo still has a copy of the file in it's history, and if you try to push to another repository (like one hosted at GitHub) then Git requires the remote repo has the same history that your local repo does (ie the same big files in it's history).

<h3>How can I can I get GitHub to accept my repo?</h3>

You need to clean the Git history of your project locally, removing the unwanted big files from all of history, and then use only the 'cleaned' history going forward. The Git commit ids of the affected commits will change.

<h3>How do I clean big files out of my Git repo?</h3>

The best tool for cleaning unwanted big files out of Git history is the <a href="https://rtyley.github.io/bfg-repo-cleaner/" rel="noreferrer">BFG Repo-Cleaner</a> - it's a simpler, faster alternative to <code>git-filter-branch</code> specifically designed for removing unwanted files from Git history.

Carefully follow the <a href="https://rtyley.github.io/bfg-repo-cleaner/#usage" rel="noreferrer">usage instructions</a>, the core part is just this:

<pre><code>$ java -jar bfg.jar --strip-blobs-bigger-than 100M my-repo.git
</code></pre>

Any files over 100MB in size (that aren't in your latest commit) will be removed from your Git repository's history. You can then use <code>git gc</code> to clean away the dead data:

<pre><code>$ git gc --prune=now --aggressive
</code></pre>

The BFG is typically at least <a href="https://docs.google.com/spreadsheet/ccc?key=0AsR1d5Zpes8HdER3VGU1a3dOcmVHMmtzT2dsS2xNenc#gid=0" rel="noreferrer">10-50x</a> faster than running <code>git-filter-branch</code>, and generally a lot easier to use.

Full disclosure: I'm the author of the BFG Repo-Cleaner.

entityMap|blocks|key|4i1j5|text|如果你在寻求帮助之前已经在摆弄你的repo，这里有一些我发现非常有帮助的东西。第一种类型：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|6mqv8|git+status|code-block|syntax|javascript|709o2|在此之后，您应该会看到类似以下内容的内容|dp8u1|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|93v18|重要的部分是"2次提交“！从这里开始，输入：|6o3|git+reset+HEAD~|dast9|因此，对于上面的示例，可以输入：|87l61|git+reset+HEAD~2|a2dv8|在你输入之后，你的"git状态“应该会显示：|5fqem|On+branch+master
Your+branch+is+up+to+date+with+'origin/master'.

nothing+to+commit,+working+tree+clean|6nv6t|从那里，您可以删除大文件(假设您还没有这样做)，并且您应该能够在不丢失工作的情况下重新提交所有内容。|3iql|我知道这不是一个超级花哨的回复，但我希望它能有所帮助！^0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|11|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|12|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|13|9|@]|A|@]|B|$]]|$2|J|4|K|6|E|8|14|9|@]|A|@]|B|$F|G]]|$2|L|4|M|6|7|8|15|9|@]|A|@]|B|$]]|$2|N|4|O|6|E|8|16|9|@]|A|@]|B|$F|G]]|$2|P|4|Q|6|7|8|17|9|@]|A|@]|B|$]]|$2|R|4|S|6|E|8|18|9|@]|A|@]|B|$F|G]]|$2|T|4|U|6|7|8|19|9|@]|A|@]|B|$]]|$2|V|4|W|6|E|8|1A|9|@]|A|@]|B|$F|G]]|$2|X|4|Y|6|7|8|1B|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1C|9|@]|A|@]|B|$]]]]

Here's something I found super helpful if you've already been messing around with your repo before you asked for help. First type: 

<pre><code>git status
</code></pre>

After this, you should see something along the lines of 

<pre><code>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
</code></pre>

The important part is the "2 commits"! From here, go ahead and type in:

<pre><code>git reset HEAD~&lt;HOWEVER MANY COMMITS YOU WERE BEHIND&gt;
</code></pre>

So, for the example above, one would type:

<pre><code>git reset HEAD~2
</code></pre>

After you typed that, your "git status" should say:

<pre><code>On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
</code></pre>

From there, you can delete the large file (assuming you haven't already done so), and you should be able to re-commit everything without losing your work. 
I know this isn't a super fancy reply, but I hope it helps!

entityMap|blocks|key|f3aup|text|这对我很有效。github压缩Git提交git重置原点/主站的文档|type|unstyled|depth|inlineStyleRanges|entityRanges|data|71coq|git+checkout+master+&&+git+pull;
git+merge+feature_branch;
git+add+.+--all;
git+commit+-m+"your+commit+message"|code-block|syntax|javascript|eimgo|查找文档|1ff3i|这里^0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|M|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|N|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|O|9|@]|A|@]|B|$]]]]

this worked for me. documentation from github
Squashing Git Commits
git reset origin/master

<pre><code>git checkout master &amp;&amp; git pull;
git merge feature_branch;
git add . --all;
git commit -m "your commit message"
</code></pre>

find documentation <a href="https://gist.github.com/patik/b8a9dc5cd356f9f6f980" rel="nofollow noreferrer">here</a>

entityMap|blocks|key|1o8q7|text|我正在补充第一个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|85rbk|git筛选器-分支--索引-筛选器'git+rm+-r+--cached+--忽略-不匹配‘头|d20fn|37g36|将会有一些来自源/主节点的合并冲突。|7rqn8|你的分支和‘源/主’已经分开，分别有114和109个不同的提交。(使用"git+pull“将远程分支合并到您的分支中)|1vrha|5l8t6|请运行此命令|6ah4s|git重置--硬原点/主节点|f1ee2|5ap96|它将丢弃所有暂存和未暂存的更改，忘记当前本地分支上的所有内容，并使其与原始/主分支完全相同。^0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|R|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|S|9|@]|A|@]|B|$]]|$2|E|4|-4|6|7|8|T|9|@]|A|@]|B|$]]|$2|F|4|G|6|7|8|U|9|@]|A|@]|B|$]]|$2|H|4|I|6|7|8|V|9|@]|A|@]|B|$]]|$2|J|4|-4|6|7|8|W|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|X|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|Y|9|@]|A|@]|B|$]]|$2|O|4|-4|6|7|8|Z|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|10|9|@]|A|@]|B|$]]]]

I am adding to the first answer.

<blockquote>
 git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch ' HEAD
</blockquote>

There will be some merge conflict from origin/master.

<blockquote>
 Your branch and 'origin/master' have diverged,
 and have 114 and 109 different commits each, respectively.
 (use "git pull" to merge the remote branch into yours)
</blockquote>

Please run this 

<blockquote>
 git reset --hard origin/master 
</blockquote>

It will throw away all my staged and unstaged changes, forget everything on my current local branch and make it exactly the same as origin/master.

entityMap|blocks|key|8plb|text|所以我遇到了一个特殊的情况:我从gitlab克隆了一个存储库，其中包含一个大于100mb的文件，但在git历史中的某个时候被删除了。后来，当我添加了一个新的github私有存储库，并试图推送到新的存储库时，我得到了臭名昭著的‘文件太大’错误。在这一点上，我不再有权访问原始的gitlab代码库。但是，我仍然能够使用以下命令推送到新的私有github存储库|type|unstyled|depth|inlineStyleRanges|entityRanges|data|79uku|在我机器上的本地存储库上：|1d9fq|$+cd+~
$+curl+https://repo1.maven.org/maven2/com/madgag/bfg/1.13.0/bfg-1.13.0.jar+>+bfg.jar
$+cd+my-project
$+git+gc
$+cd+../
$+java+-jar+bfg.jar+--strip-blobs-bigger-than+100M+my-project
$+cd+my-project
$+git+reflog+expire+--expire=now+--all+&&+git+gc+--prune=now+--aggressive
$+git+remote+-v+#+confirm+origin+is+the+remote+you+want+to+push+to
$+git+push+origin+master|code-block|syntax|javascript^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|J|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|K|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|L|9|@]|A|@]|B|$H|I]]]]

So I encountered a particular situation: I cloned a repository from gitlab, which contained a file larger than 100 mb, but was removed at some point in the git history. Then later when I added a new github private repo and tried to push to the new repo, I got the infamous 'file too large' error. By this point, I no longer had access to the original gitlab repo. However, I was still able to push to the new private github repo using <code>bfg-repo-cleaner</code> on a LOCAL repository on my machine:

<pre><code>$ cd ~
$ curl https://repo1.maven.org/maven2/com/madgag/bfg/1.13.0/bfg-1.13.0.jar &gt; bfg.jar
$ cd my-project
$ git gc
$ cd ../
$ java -jar bfg.jar --strip-blobs-bigger-than 100M my-project
$ cd my-project
$ git reflog expire --expire=now --all &amp;&amp; git gc --prune=now --aggressive
$ git remote -v # confirm origin is the remote you want to push to
$ git push origin master
</code></pre>

entityMap|blocks|key|259t5|text|git+lfs+migrate+import+--include="fpss.tar.gz"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|6ulad|这应该用新的lfs引用重写本地提交|unstyled|6prel|https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-migrate.1.ronn?utm|90lce|_|fho2b|source=gitlfs|210ig|826p8|站点utm|3372m|cgnas|medium=doc|79p1u|a1882|男人|69vua|3ijtn|迁移|8fbv3|730nf|链接utm|a6dcr|8fdh1|campaign=gitlfs#examples^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|15|9|@]|A|@]|B|$C|D]]|$2|E|4|F|6|G|8|16|9|@]|A|@]|B|$]]|$2|H|4|I|6|G|8|17|9|@]|A|@]|B|$]]|$2|J|4|K|6|G|8|18|9|@]|A|@]|B|$]]|$2|L|4|M|6|G|8|19|9|@]|A|@]|B|$]]|$2|N|4|K|6|G|8|1A|9|@]|A|@]|B|$]]|$2|O|4|P|6|G|8|1B|9|@]|A|@]|B|$]]|$2|Q|4|K|6|G|8|1C|9|@]|A|@]|B|$]]|$2|R|4|S|6|G|8|1D|9|@]|A|@]|B|$]]|$2|T|4|K|6|G|8|1E|9|@]|A|@]|B|$]]|$2|U|4|V|6|G|8|1F|9|@]|A|@]|B|$]]|$2|W|4|K|6|G|8|1G|9|@]|A|@]|B|$]]|$2|X|4|Y|6|G|8|1H|9|@]|A|@]|B|$]]|$2|Z|4|K|6|G|8|1I|9|@]|A|@]|B|$]]|$2|10|4|11|6|G|8|1J|9|@]|A|@]|B|$]]|$2|12|4|K|6|G|8|1K|9|@]|A|@]|B|$]]|$2|13|4|14|6|G|8|1L|9|@]|A|@]|B|$]]]]

<pre><code>git lfs migrate import --include="fpss.tar.gz"
</code></pre>

this should re-write your local commits with the new lfs refs 

<a href="https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-migrate.1.ronn?utm_source=gitlfs_site&amp;utm_medium=doc_man_migrate_link&amp;utm_campaign=gitlfs#examples" rel="nofollow noreferrer">https://github.com/git-lfs/git-lfs/blob/master/docs/man/git-lfs-migrate.1.ronn?utm_source=gitlfs_site&amp;utm_medium=doc_man_migrate_link&amp;utm_campaign=gitlfs#examples</a>

entityMap|blocks|key|27ief|text|将大文件/文件夹保留在工作文件夹中的解决方案|type|unstyled|depth|inlineStyleRanges|entityRanges|data|e8htf|这是用来解决这里所问问题的那一行(来自答案1)：|fbff|如果文件/dir在工作树中，此命令还会删除文件/dir。|af5jl|如果您希望将文件/文件夹保留在工作树中，我建议采取以下步骤。|5slt5|在该错误之后运行|6ltc3|将有问题的文件/文件夹添加到|b59ej|.gitignore`|bfvbq|文件。|daeul|照常进行|dqbjl|它可以捕获其他文件/文件夹，但必须捕获|8oe19|文件。接下来是|6r4eu|最后^0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|Y|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Z|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|10|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|11|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|12|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|13|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|14|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|15|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|16|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|17|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|18|9|@]|A|@]|B|$]]|$2|W|4|X|6|7|8|19|9|@]|A|@]|B|$]]]]

The solution to keep the large files/folders within the working folder

This is the line that worked to solve the problem asked here (from answer 1):

<code>git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch &lt;file/dir&gt;' HEAD</code>

This command also delete the file/dir if the file/dir is within the working tree.

If you want to keep the file/folder within the working tree I propose taking the following steps.

<ol>
<li>After that error run <code>git reset HEAD^</code></li>
<li>Add the file/folder in question into ``.gitignore``` file.</li>
<li>Proceed as usual <code>git add .</code> which might capture other files/folders but must capture <code>.gitignore</code> file. Next is <code>git commit -m"message"</code> and finally <code>git push origin &lt;branch_name&gt;</code></li>
</ol>

entityMap|blocks|key|eiq59|text|有时会将文件保存在跟踪历史记录中，请尝试以下步骤：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5b5cn|，如果您正在查看|8vesn|创建模式|dvvht|列出大文件，然后执行以下操作：|454mc|..。您应该会看到控制台中显示了一系列重写，这些重写以：|3e2bq|rm+'filename‘和|a3fbf|最后一行|30a8t|参考|fig0k|被重写了。|dlhqe|已经完成了。^0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|U|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|V|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|W|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|X|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|Y|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|Z|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|10|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|11|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|12|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|13|9|@]|A|@]|B|$]]]]

Sometimes the file is kept in tracking history, try the following steps:

<ol>
<li><code>git commit</code>, If you are seeing create mode with the big file listed, then do:</li>
<li><code>git filter-branch --index-filter 'git rm -r --cached --ignore-unmatch filename' HEAD</code>.
You should see a bunch of Rewrites shown in your console which ends with:

rm 'filename' and 

the last line Ref was rewritten.</li>
</ol>

It's done.

entityMap|blocks|key|t965|text|我的非正统但简单的从头开始的解决方案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|8gjqn|忘了你最近有问题的本地git仓库吧|a5ujv|将您的存储库添加到一个全新的新目录中。|3h15s|8bibi|在这一点上，只需复制您的新文件提交，到您的新本地代表从旧的可能包括您现在减少的巨大文件(S)。|f4jdc|瞧！对我来说就像个护身符。^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|L|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|M|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|N|9|@]|A|@]|B|$]]|$2|G|4|-4|6|7|8|O|9|@]|A|@]|B|$]]|$2|H|4|I|6|7|8|P|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|Q|9|@]|A|@]|B|$]]]]

My unorthodox but simple solution from scratch:
<ul>
<li>just forget about your recent problematic local git repository and <code>git clone</code> your repository into a fresh new directory.</li>
<li><code>git remote add upstream &lt;your github rep here&gt;</code></li>
<li><code>git pull upstream master</code></li>
<li>at this point just copy your new files to commit, to your new local rep from the old one may be including your now reduced giant file(s).</li>
<li><code>git add .</code></li>
<li><code>git commit -m &quot;your commit text here&quot;</code></li>
<li><code>git push origin master</code></li>
</ul>
voila! worked like a charm in my case.

entityMap|blocks|key|1ckq|text|与其做复杂的事情，不如把你的repo+(在你的计算机上)复制到另一个地方。删除大文件。做几个推拉动作。那么你的一些文件就会被像“<+HEAD”这样的东西弄得乱七八糟。只需将备份复制到磁盘上的旧文件夹中即可。再做一次add，commit，push！|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

rather than doing complicated stuff, copy your repo (on your computer) to another place. delete the large file. do a couple of push and pull. Then some of your files will be messed up having things like &quot;&lt;&lt;&lt;&lt;&lt;&lt; HEAD&quot;. Just copy your backup into the old folder on the disk. Do another add, commit, push!

entityMap|blocks|key|edu1g|text|使您的本地存储库与远程存储库匹配：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|50s04|git+reset+--hard+origin/master|code-block|syntax|javascript|fk26j|然后再推一次。^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|J|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|K|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|L|9|@]|A|@]|B|$]]]]

Make your local repo match the remote repo with:
<pre><code>git reset --hard origin/master
</code></pre>
Then push again.

entityMap|blocks|key|3uq4t|text|当我的iOS项目中没有gitignore文件时，我遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|81chs|我认为也许它试图将一个巨大的文件推送到github，而github可能拒绝了这个巨大的文件或(文件)^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

I had this issue when I didn't have a gitignore file with my iOS project
I think maybe it was trying to push a humungous file to github and github was probably rejecting that giant file or (files)

entityMap|blocks|key|e0p8t|text|如果你上传的是你自己的项目，那么只需要进入目录所在的文件即可。删除大文件。然后点击“查看”(窗口文件)查看->检查隐藏文件夹，然后您将能够看到'+.git‘文件删除.git文件这将删除您的所有提交历史记录，然后您可以像新的一样推送您的存储库...|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

if you are uploading your own project then just go the file where directory is present.
Delete large file.
then click on the &quot;view&quot;(window file)
view-&gt; check hidden folder
then you will be able to see '.git' file
delete .git file
this will delete all your commit history
Then you can push your repo like new one...

Currently I have

<ol>
<li>Empty GitHub repo</li>
<li>SSH server repo (main)</li>
<li>Local Repo</li>
</ol>

SSH server repo was the most up-to-date repo (production site) so I did a Git clone from there to local. I then tried to do a <code>git push</code> to GitHub.

Everything went OK but then it said something about filename.gz being too large for GitHub. I didn't need this file so I ran several Git commands to get rid of it from Git cache then pushed back to SSH server.

I don't see the large file locally but it's still on SSH server even though <code>git diff</code> returns nothing and git push returns "Everything is up-to-date" - And even though the file is not visible in local repo when I try to push to GitHub I still get error about it 

<blockquote>
 remote: error: File fpss.tar.gz is 135.17 MB; this exceeds GitHub's file size limit of 100 MB
</blockquote>

I followed steps under "fixing the problem" <a href="http://help.github.com/articles/working-with-large-files">listed on GitHub help</a> so shouldn't that have been enough?

How is the file still in the ether when it's not local or listed in git status/diff/push?

Can't push to GitHub because of large file which I already deleted

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

 目前我有 空的GitHub存储库 SSH服务器存储库(主) 本地回购 SSH服务器存储库是最新的存储库(生产站点)，所以我从那里克隆了一个Git到本地。然后我试着做一个 为GitHub干杯。 一切都很顺利，但是它说了一些关于filename.gz对于GitHub来说太大的问题。我不需要这个文件，所以我运行了几个Git...

问无法推送到GitHub，因为我已经删除了大文件
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法推送到GitHub，因为我已经删除了大文件EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问无法推送到GitHub，因为我已经删除了大文件
EN