Caleb Maclennan

@skorokithakis This issue seems to be about the current lock/unlock state of the workng copy, not the encrypted/plain state of the repository object store. Different problem and `git crypt status`...

Presumably your deployment system would pass along the required credentials ... a GPG private key or a passphrase as an environment variable. The secret passed along in memory as part...

This issue has nothing to do with `git-crypt`, you need to look into how your GPG tools work. I'm not on Windows so I don't know what your process will...

I assume you are using Ubuntu. Ubuntu has had packaging for `git-crypt` in their universe repository since 16.04 (xenial). Note that this is downstream from Debian packaging which has had...

This really isn't a question about `git-crypt` so much as how to use GPG. You need to export your secret keys from one machine and import them on the other....

I'm designing the deploy process for a current project under the assumption that this is possible, but I haven't actually scripted the CI end yet. In your version would the...

1. Checkout and unlock a copy of the repository. 2. Remove the relevant attribute filter lines. 3. `git-add` the unlocked state of the files that were previously encrypted from your...

Presumably it needs rebuilding for new libraries. Either you can do this yourself from source, or poke whoever maintains the binary package you referred to so they rebuild on macOS...

This does not sound very smart. There are too many possible edge cases (such as other clean/fudge filters) that could cause this to go wrong. Requiring a clean state makes...

@AGWA Would you accept a fix for this if a PR was put together?