We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We are doing a lot of secrets work right now and we have more than once forgotten to press Edit before changing the file which sops doesn't like.
Can the plugin mark the file as read/only so the only way to change it is to press Edit?
The text was updated successfully, but these errors were encountered:
I will have a good think about while im on vacation (:
I will get back to you in about 2 weeks.
Sorry, something went wrong.
I added the posibility to mark all sops files as read only as an option.
You can test this out with the latest release:
I will publish this to the jetbrains marketplace once i had the time to test it a bit more myself.
Sry work was overwhelming lately and I completly forgot about it.
I published the plugin and its currently pending approval.
No branches or pull requests
We are doing a lot of secrets work right now and we have more than once forgotten to press Edit before changing the file which sops doesn't like.
Can the plugin mark the file as read/only so the only way to change it is to press Edit?
The text was updated successfully, but these errors were encountered: