You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When cutting a commit, it lets you choose which patches to include in the first commit, but it doesn’t show anything for empty files that are created, meaning that all empty file creations will end up in the second commit.
At least slightly related to #33 which is about binary changes always ending up in the second commit.
The text was updated successfully, but these errors were encountered:
Thanks for the report! I agree that this is a similar situation to #33, caused by limitations of git reset --patch, which is used to show the hunk picker.
This should be fixable by providing our own interface for selecting which commit these non-patch files end up in.
When cutting a commit, it lets you choose which patches to include in the first commit, but it doesn’t show anything for empty files that are created, meaning that all empty file creations will end up in the second commit.
At least slightly related to #33 which is about binary changes always ending up in the second commit.
The text was updated successfully, but these errors were encountered: