Vault merge conflicts and vault pull/clone edge cases #162
Labels
development
Standard development
r&d:polykey:core activity 1
Secret Vault Sharing and Secret History Management
When pulling changes for a vault, if merge conflicts arise, they need to be rejected at this stage as there is no ability for users to resolve the merge conflicts
Also, the edge cases for vault cloning and pulling need to be considered. For example, if a user clones a vault and while pulling from the vault the git history does not match the expected results this should be rejected
Additional Context
The text was updated successfully, but these errors were encountered: