Repository navigation
Complete dump paths on restore and confirm before restoring a file - #22
Merged
Merged
Conversation
joelwurtz
force-pushed
the
feat/restore-completion
branch
from
October 6, 2026 11:47
921e158 to
14b432a
Compare
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.
{service}:restorenow completes the path of the dump, suggesting directories and files matching the formats of the service.Restoring a file asks for confirmation first, which
--forceskips, while a dump piped through the standard input is restored straight away. The worktree database copy passes--forceso it stays non-interactive.