feat: add safer restore modes#25
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds safer restore choices to the TUI so users are not forced through
git reset --hardfor every recovery path.Enterremains the hard-reset flow, but it now creates a backup ref first;sperforms a soft reset, andcchecks out the selected commit in detached HEAD.The confirmation dialog now shows the exact Git command before execution, and full diff preview now compares
HEADagainst the selected target so the preview matches restore semantics instead of showing only the selected commit's patch.Closes #17.
Verification
cargo fmt --checkcargo clippy -- -D warningscargo testcargo buildgit diff --checkcargo run -- --help