This repository has been archived by the owner on Nov 1, 2022. It is now read-only.
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.
This commit tries to add support for git-crypt. While I'm aware that both git-secret and sops are already supported, our team (and I'm sure many others) rely on git-crypt and since the additional support is quite trivial, I'm asking for including it.
We are in progress of moving our processes to flux, and as we saw that you support git-secret our first thought was simply "ok let's change our repo to it then". But the more we had to work with it the less we liked it. The main reasons are:
git secret reveal
&& editing something &&git secret hide
) results by default in a re-encryption of all of the secret files (in our case more than 100 files) which pollutes historygit status
First #1676 asked for crypto support, but that ended up implementing git-secret in #2159. This commit would also solve conversations like #2904
Please tell me if I can improve something and I will.