test: ignore global config in tests

[sandr01d]

Check list

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have added unit tests for my code
• I have made corresponding changes to the documentation

Description

When creating commits in tests, it's best to pass the --no-gpg-sign flag. I have commit.gpgsign set to true in my git config. Without --no-gpg-sign, git wants me to enter a passphrase when running the tests, which is a bit annoying.

Type of change

• Bug fix
• New feature
• Refactor
• Breaking change
• Test
• Documentation change

Test environment

• Shell
  • bash
  • zsh
  • fish
• OS
  • Linux
  • Mac OS X
  • Windows
  • Others:

[cjappl]

Is there a way to be able to pass "ignore the gitconfig" to these git commands? I think ideally all these tests would be completely independent of local gitconfig. It would be unexpected to have flakiness from that.

[carlfriedrich]

I would also vote for trying to find a way to completely ignore the user's .gitconfig. As far as I can see, there is no option for git to do so, though.

Maybe we can set the HOME env variable for a test to a temp directory? This way, the user's config shouldn't be picked up at first. Not sure if this might have side effects, though.

[cjappl]

Possibly relevant?

https://superuser.com/questions/53030/run-git-commands-without-default-gitconfig

May be removed though, someone does recommend doing something like HOME= git ..., which does seem a little sketchy. Maybe worth a try but I'd be worried too

[carlfriedrich]

@cjappl Good find, and good idea setting HOME for the git call only. IMO that should be safe.

[sandr01d]

I've found another option, which I'd prefer. When GIT_CONFIG_GLOBAL and GIT_CONFIG_SYSTEM is set to /dev/null, git will ignore the global config file. You can find more details here.

[carlfriedrich]

@sandr01d Ah, great find. That makes sense. Approved!