Describe the feature
When resetting a branch to a commit, Neo Git Graph offers Soft, Mixed, and Hard reset modes. I like to use --keep from the CLI to change files in the working directory like --hard, but prevent discarding uncommitted work the way it does (since it will abort the reset if it has to overwrite any files, allowing me to check that I want to delete unsaved changes while moving the current branch).
Problem it solves
Move the current branch to a new commit without losing uncommitted files. (You lose the current commit hash if it's unreachable through other refs, but can find the hash from the reflog.)
Proposed solution
Add a new option to "Are you sure you want to reset the current branch to commit ...?" for --keep. (Git Extensions also has a --merge, but I have not found a use for it and have lost data from experimenting with it in the past.)
Describe the feature
When resetting a branch to a commit, Neo Git Graph offers Soft, Mixed, and Hard reset modes. I like to use --keep from the CLI to change files in the working directory like --hard, but prevent discarding uncommitted work the way it does (since it will abort the reset if it has to overwrite any files, allowing me to check that I want to delete unsaved changes while moving the current branch).
Problem it solves
Move the current branch to a new commit without losing uncommitted files. (You lose the current commit hash if it's unreachable through other refs, but can find the hash from the reflog.)
Proposed solution
Add a new option to "Are you sure you want to reset the current branch to commit ...?" for --keep. (Git Extensions also has a
--merge, but I have not found a use for it and have lost data from experimenting with it in the past.)