Bug Report
git-team version: 1.7.0
go version: 1.17.7
failure description
Invoking git team assignments add noujz "Mr. Noujz <noujz@mr.se>" exits with error: exit status 255 if no $HOME/.gitconfig is present.
This also happens if the file is read-only.
Background:
It's possible to store gitconfig under $XDG_HOME, e.g. $HOME/.config/git/config
Git checks a set of paths for configurations on every invocation.
expected behaviour description
Creation of $HOME/.gitignore or another distinct file for git-team.
Alternatively or additionally a graceful exit with an explanation error message or offering to create a .gitconfig.
Note: Some approaches like home-manager favours immutable configuration, meaning that wherever gitconfig is put it is read-only by default. That's not always a given and it's possible to make them writeable as well.
PS:This also happens for other git-team cmd's that rely on the existence of the file like git-team disable.
Bug Report
git-team version: 1.7.0
go version: 1.17.7
failure description
Invoking
git team assignments add noujz "Mr. Noujz <noujz@mr.se>"exits witherror: exit status 255if no$HOME/.gitconfigis present.This also happens if the file is read-only.
Background:
It's possible to store gitconfig under $XDG_HOME, e.g. $HOME/.config/git/config
Git checks a set of paths for configurations on every invocation.
expected behaviour description
Creation of $HOME/.gitignore or another distinct file for git-team.
Alternatively or additionally a graceful exit with an explanation error message or offering to create a .gitconfig.
Note: Some approaches like home-manager favours immutable configuration, meaning that wherever gitconfig is put it is read-only by default. That's not always a given and it's possible to make them writeable as well.
PS:This also happens for other git-team cmd's that rely on the existence of the file like
git-team disable.