Re: git config: unintuitive behaviour with --global and --no-includes
Ben Knoble <[email protected]>
| Newsgroups | org.kernel.vger.git |
|---|---|
| Message-ID | <[email protected]> |
> Le 20 juil. 2026 à 06:02, Hendrik Jaeger <[email protected]> a écrit : > > Hi > > I ran into a problem working with lbmk (https://codeberg.org/libreboot/lbmk). > To see whether git is correctly configured, it runs `git config --global user.name` and that failed for my setup. > The reason is that I have user.name and user.email not directly in the normal git config file but in an included file and when given a scope like --global `git config` does not by default check included files. [snip] > Regarding the initial issue: I just added --includes to the call in lbmk and it works just fine, so there is no need to address this. I wonder why not use « git config user.name » without scope? That seems to sidestep the problem. Unless there’s a reason to use global-scope only? There’s also « git var GIT_AUTHOR_IDENT ».