Wizard: handle an existing store with no matching key #9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the README roadmap.
When the store exists (e.g. after a clone) but none of the keys in
keys/can decrypt for the recipients in.gpg-id, the first-run wizard has no path forward. This is the likely first-run case for anyone with an existingpasssetup.To do:
.gpg-id).Blocks 0.1.0.
The basic path (clone a store, then import the key it's encrypted to) already worked. Two dead ends remained:
.gpg-id(e.g. an empty repository) landed on that import step with no recipientsThe draft PR from branch
wizard-missing-keyfixes both. It adds a guarded Start over, which deletes the local clone only if the remote had everything in it at the last sync. It also sets up an empty clone in place.