You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just started to use git-crypt to protect some of our config files.
One thing we noticed is that setting .gitattributes filter seems to interfere with text=auto eol=lf attributes.
How can I enforce the git-crypt protected secrets to use LF as EOL?
In my case, here's how my .gitattributes looks like:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I just started to use
git-crypt
to protect some of our config files.One thing we noticed is that setting .gitattributes
filter
seems to interfere withtext=auto eol=lf
attributes.How can I enforce the
git-crypt
protected secrets to use LF as EOL?In my case, here's how my .gitattributes looks like:
While staging two CRLF files (a
*.md
file and a*.enc
secret), the former has its CRLF normalized to LF while the latter is not.Ideally, we would like to have secrets such as
secret.enc
normalized to LF beforegit-crypt
clean (encrypt) them.Yet we can not figure out how to.
Beta Was this translation helpful? Give feedback.
All reactions