Konubinix' opinionated web of thoughts

Git Gc: Error: Could Not Read 0000000000000000000000000000000000000000

fleeting

git

harmless in the sense that it does not indicate a broken repository

https://stackoverflow.com/questions/71364717/git-gc-error-could-not-read-0000000000000000000000000000000000000000

bug that was introduced in Git 2.35 and that should be fixed in later releases. [Edit: This regression was fixed in Git 2.36.0.]

https://stackoverflow.com/questions/71364717/git-gc-error-could-not-read-0000000000000000000000000000000000000000

worst that can happen is that git gc does not prune all objects that are referenced from reflogs. The error is triggered by an invocation of git reflog expire –all that git gc does behind the scenes.

https://stackoverflow.com/questions/71364717/git-gc-error-could-not-read-0000000000000000000000000000000000000000

trigger are empty reflog files in the .git/logs directory structure that were left behind after a branch was deleted.

https://stackoverflow.com/questions/71364717/git-gc-error-could-not-read-0000000000000000000000000000000000000000

workaround you can remove these empty files

https://stackoverflow.com/questions/71364717/git-gc-error-could-not-read-0000000000000000000000000000000000000000