Repository navigation
Global gitconfig fails to copy to devcontainer with postCreateCommand #787
Description
Activity
We could ignore the empty
[user]section. As a workaround you can comment out the[user]line as# [user].Reacted by Avin ZarlezI confirmed manually removing the global file ( or commenting out the empty user section ) does make it so the proper global file will be copied. Although that is a manual step that may be annoying/easy to miss/hard to explain to developers when making a fresh container.
I think ignoring an empty
[user]section is ideal.On a related note:
~/.config/git/config
[include] path = ~/.config/git/local~/.config/git/local
[user] name = Example User email = example@example.comhttps://git-scm.com/docs/git-config#_includes
https://git-scm.com/docs/git-config#Documentation/git-config.txt-includepath
https://git-scm.com/docs/git-config#Documentation/git-config.txt---no-includesI am running into the same issue. For me, the problem was that the
postCreateCommandhad a non-zero exit code.When I added
./my-setup-script.sh || exit 0then the global.gitconfigwas made available inside the container again.Reacted by James Holwell and Lucas Hoz
Related to this issue #98 there still seems to be a problem for the global git config.
My local git config is copied, but my global git config is not. Settings that only existed in my global config like my name and email are not copied.
It seems that a default empty global git config is created when using
postCreateCommand. In my case, I am running a script"postCreateCommand": "sh ./scripts/env-setup.sh"Here is what my containers global git config looks like when using
postCreateCommand:If I change it to
postAttachCommand, then an exact copy of my actual global git config file from my machine is copied correctly into the dev container.