Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note for renaming vaults #448

Merged
merged 1 commit into from
Nov 13, 2023
Merged

Add note for renaming vaults #448

merged 1 commit into from
Nov 13, 2023

Conversation

Cassie205
Copy link
Contributor

No description provided.

@Cassie205 Cassie205 linked an issue Nov 10, 2023 that may be closed by this pull request
1 task
@Cassie205 Cassie205 requested a review from tatze96 November 10, 2023 15:55
@dkocher dkocher self-requested a review November 10, 2023 18:18
@tatze96 tatze96 merged commit 033a580 into main Nov 13, 2023
2 checks passed
@tatze96 tatze96 deleted the issue/442 branch November 13, 2023 08:53
@@ -141,6 +141,10 @@ Passwords are saved in the *Credential Manager*. You can view and delete your sa

File transfers require you to unlock the vault again unless you have chosen to save your vault passphrase in the keychain.

### Renaming

Make sure that the vault is locked before it gets renamed. Otherwise the vault will be changed to a normal folder. Using [Smart Synchronization](../mountainduck/connect/sync.md) mode an additional vault with the original name will appear.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add to bullet items for what is expected when renaming a locked|unlocked vault.

@@ -141,6 +141,10 @@ Passwords are saved in the *Credential Manager*. You can view and delete your sa

File transfers require you to unlock the vault again unless you have chosen to save your vault passphrase in the keychain.

### Renaming

Make sure that the vault is locked before it gets renamed. Otherwise the vault will be changed to a normal folder. Using [Smart Synchronization](../mountainduck/connect/sync.md) mode an additional vault with the original name will appear.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the previous vault remains this is a bug and an issue should be opened instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Renaming unlocked Cryptomator vaults
3 participants