4 ms·

Oh I am really digging the change to allow directory level configs for config settings. I have commited with my work credentials to open source projects more t

• pawadu 9y ago
  Not uncommon! This is why .gitignore is the first thing I explain to git newcomers.
  • matt_kantor 9y ago
    I think you misread the parent comment. They didn't say "committed my work credentials", it was "committed with my work credentials". As in they have two different identities and used the wrong one when committing a change, so the commit author was incorrect. Being able to set configs per directory provides a workaround.
    • pawadu 9y ago
      Yeah I totally misread that... Nevertheless, .gitignore should still be the first thing you learn about git :)
• simias 9y ago
  Indeed. My current workaround was simply not to put any email in ~/.gitconfig. Upon commiting for the first time in a new repo git would complain, then I could set the correct email for this particular repo using `git config user.email $email`.
  • dmit 9y ago
    I think this only works if you set `git config --global user.useconfigonly true`, otherwise git will try to guess your name/email.
    • simias 9y ago
      It does, thank you for that tip! So far I'd just `git commit --amend --reset-author` after setting the email the first time.