3 ms·
I had to go back to the man pages. I think I got stuck at the "Unlike .gitignore, negative patterns are forbidden." and missed that you could unset attributes i
by zimbatm 13y ago
I had to go back to the man pages. I think I got stuck at the "Unlike .gitignore, negative patterns are forbidden." and missed that you could unset attributes instead :)
In the process I also found `git check-attr` that goes 90% of the way of the `git crypt check` idea. Eg: `git check-attr -a -- path/to/file` will output git-crypt if the file is encrypted. A `git crypt ls` that lists all the encrypted files could be useful too to give more visibility.
- agwa 13y ago> In the process I also found `git check-attr` that goes 90% of the way of the `git crypt check` idea. Eg: `git check-attr -a -- path/to/file` will output git-crypt if the file is encrypted. A `git crypt ls` that lists all the encrypted files could be useful too to give more visibility. That's extremely useful - thanks for passing on that info!