-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Empty/inaccessible SecretAgent/Data
directory
#486
Comments
What version are you using? I fixed something that sounds similar to this in the last update. |
I have "Version 2.3.1 (1.5638740552)". |
The reason for the |
@torarnv thanks for the feedback, that seems to work! I wonder if there's way I can avoid granting permission to all of VS Code and still use this with git in VS Code's Terminal tabs... |
A solution like outlined in #499 (comment) would help with that. |
I think we would also need to write the |
I started looking at setting up git commit signing yesterday per the instructions in #441. However, when I look at my
~/Library/Containers/com.maxgoedjen.Secretive.SecretAgent
dir usingls -l
I get an error:I've already tried killing the Secretive processes, but this doesn't appear to help. Adding a new key also doesn't seem to change anything.
The text was updated successfully, but these errors were encountered: