Dragging a changed file from a commit to an empty commit above destroys the empty commit above

[Kimeiga]

Version

0.14.8

Operating System

macOS

Distribution Method

dmg (Mac OS - Apple Silicon)

Describe the issue

If you create an empty commit above a commit and drag a changed file to it, that empty commit above disappears after the app finishes loading the situation, and that changed file goes back to the Changed files list on the first commit.

This doesn't happen if you create an empty commit below and then drag a changed file into there.

How to reproduce (Optional)

1. Create a commit with a changed file
2. Create an empty commit above
3. Drag the changed file to the empty commit above
4. Observe it going away

Expected behavior (Optional)

The empty commit above should remain and have the changed file in it, just like what happens when you drag a changed file to an empty commit below

Relevant log output (Optional)

[Byron]

Thanks a lot for reporting.

While trying to reproduce this issue, I think I ran into a couple of other unexpected issues related to dragging and dropping files, which probably means that what is described here is also likely to happen. It's probably best to start on a cleaner slate than what I am using for testing, too.

It's good to know that we are working on a complete overhaul of the underlying code and one may hope that it will work much better.