![]() If others already cloned your repo before, a bit of communication is in order to warn them. ![]() ![]() Deltarune Chapters 3, 4, and 5 Download for free and play full version of Deltarune. Note that you will have to do a git push -force after that, because the history of the more recent commits will have been modified. I uninstalled the game and it deleted everything in the folder. That will track for you that elusive large file in your repo history and remove it. Or, if you don't know but want to get rid of any large file (say > 90MB), you can use the BFG repo cleaner bfg -strip-blobs-bigger-than 90M my-repo.git In any case, you can try, as explained in " Fixing the “this exceeds GitHub’s file size limit of 100 MB” error", a filter-branch (if you know the name/path of the large file that you can't see) git filter-branch -index-filter 'git rm -cached -ignore-unmatch '. Original answer, using obsolete tools like git filter-branch or BFG: If you want to filter out all files bigger than a certain size, you can use -strip-blobs-bigger-than with some size ( K, M, and G suffixes are recognized), e.g.: git filter-repo -strip-blobs-bigger-than 10M Use git filter-repo (python-based, to be installed first) It is possible that you are pushing several commits, one of them including a large file, and another more recent one removing that file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |