Reputation: 2979
I would like to push my project into the github, however i just notice there is a file called java_pid14920.hprof inside the android folder and cause around 300MB
remote: error: File android/java_pid14920.hprof is 301.75 MB; this exceeds GitHub's file size limit of 100.00 MB
I wonder it is safe to delete this file ?
Upvotes: 32
Views: 17597
Reputation: 11457
This worked for me
git filter-branch -f --index-filter "git rm --cached --ignore-unmatch example/android/java_pid2243.hprof"
Then
git push -u origin main
Note:
My file was present in the directory like this.
example/android/java_pid2243.prof
Upvotes: 1
Reputation: 121
I ran this command. It works on Windows 10
git filter-branch -f --index-filter "git rm --cached --ignore-unmatch android/java_pid10213.hprof"
Upvotes: 8
Reputation: 447
I had two hpprof files committed; So I just ran this command, and the files have been removed successfully.
git filter-branch -f --index-filter 'git rm --cached --ignore-unmatch android/java_pid21295.hprof android/java_pid16516.hprof'
Upvotes: 5
Reputation: 597
The only answer here didn't work for me, but I found a solution that did.
My offending file was android/java_pid2325.hprof
, but yours obviously may vary. I used git filter-branch
:
git filter-branch -f --index-filter 'git rm --cached --ignore-unmatch android/java_pid2325.hprof'
Make sure to add *.hprof
to your .gitignore
and push the commit.
Note*-> Make sure to change the name of *.hprof to the same as your local *.hprof
Upvotes: 48
Reputation: 153
@bk2204 answer worked for me. In my case, .hprof files were in android/hprof.
Go to ".gitignore"
Just put this snippet.
android/
*.hprof
Upvotes: 5
Reputation: 76459
This sounds like a heap profiling output file, which you probably don't want in your repository at all. You'll want to delete it from the entire history and probably add an entry to .gitignore
to ignore *.hprof
. If the file is not in the latest commit, simply deleting it there won't make your repository pushable to GitHub; you'll have to remove the object from the entire history.
If you can easily find the commit which introduced it (try git log -- android/java_pid14920.hprof
), you can do a git rm android/java_pid14920.hprof
and then do git commit --fixup HASH-OF-COMMIT && GIT_SEQUENCE_EDITOR=true git rebase -ir --autosquash HASH-OF-COMMIT^
(note the caret) to rebase out the file.
You can also use a tool like git filter-branch
or bfg
to filter out large objects that you don't want.
Note that doing this will rewrite the history of any intervening commits, changing their object IDs.
Upvotes: 31