Replies: 1 comment
-
The commits were not empty. These were merge commits, so |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Executing
git filter-repo --prune-empty always --prune-degenerate always
doesn't prune any merge commits (all commit hashes remain the same). From the documentation, I understand that it should, but for some reason, it doesn't. Any ideas?Update: after running
git filter-repo
, the following command displays many empty commits:Beta Was this translation helpful? Give feedback.
All reactions