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
{{ message }}
Repository navigation
include.path options from git configuration are not followed #1402
At the bottom of your ~/.gitconfig put the following.
# Allow local overrides (i.e. for work)[include]path = ~/.gitconfig.local
Then create a ~/.gitconfig.local file with the following contents.
# Overrides for work
[user]
email = myself@work.com
Verify Git understands this by running git config user.email and see that it gives myself@work.com.
Another useful command is git config --list --show-origin | grep email
Proposed solution
Running git bug user new, when providing a suggestion for name, email, etc should run the appropriate Git command to retreive the default (git config user.name instead of whatever it's doing now.
Why I do this
I manage my personal dotfiles with a Git repo and stow, which seems to be a common practice.
At work I maintain a fork of this repo which has stuff like my GPG keys, my work email, etc, etc. So I put that stuff in ~/.gitconfig.local which is included from ~/.gitconfig.
Thanks for your report. The "new identity" workflow currently reads from the local and global configuration scopes, but go-git still doesn't follow includes, so this is something git-bug will need to implement itself.
changed the title [-]New user suggestions don't respect git config[/-][+]`include.path` options from git configuration are not followed[/+]on May 8, 2025
Activity
sudoforge commentedon May 8, 2025
Thanks for your report. The "new identity" workflow currently reads from the local and global configuration scopes, but go-git still doesn't follow includes, so this is something git-bug will need to implement itself.
[-]New user suggestions don't respect git config[/-][+]`include.path` options from git configuration are not followed[/+]