Stefan Haller <lists@xxxxxxxxxxxxxxxx> writes: > Our git client (lazygit) has a need to store per-repo config files that > override the global one, much like git itself. The easiest way to do > that is to store those in a .git/lazygit.cfg file, and I'm wondering if > there's any reason why this is a bad idea? An obvious alternative is to have .lazygit directory next to .git directory which would give you a bigger separation, which can cut both ways.
