git lg(i) now always uses sed to display clearer GPG verification
messages. The only difference between the two aliases now being that git
lg always displays its result in a pager
Having a non functionning git config makes unlocking the repo impossible.
However, since encrypting the git config itself probably wasn't expected by the
git-crypt developers, this does happen in this setup.
This implements a small workaround.
these files might contain private information, such as git forges' URL
or which gpg key I use for specific repos.
Basically, you would only need them if you were me.
kalmenn