Open
Conversation
Document how keystore sync works, what data gets uploaded, supported cloud providers with their encryption models, local storage locations, and practical considerations for users. Link from README keystore section to the new doc. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
The keystore cloud sync feature has zero user-facing documentation — the README has a single bullet point ("Cloud sync keystores across machines") with no detail on what data gets uploaded, which providers are supported, or how secrets are handled.
This adds
docs/keystore-sync.mdcovering:Also links the new doc from the README's keystore feature section.
Prompted by #135 — though we're skipping the formal
SECURITY.mdsuggestion, the underlying point about missing keystore sync documentation was fair.