I would say this issue is invalid, as the setup command already have a -- global option and it is explained in the man how this works. Is true that not using --global less useful than doing it locally (in particular for clone) but it is a valid use case, as you might want to have per-repo auth credentials.
The only option I see here is making --global the default and adding -- local but we try to mimic git as much as possible, and this is how git config works (which is what's used under the hood), so I would need a much stronger case for this. On Thu, 17 Sep 2015 10:43:28 -0400 Joey Hess <i...@joeyh.name> wrote: > Package: git-hub > Version: 0.9.0-1 > Severity: normal > > I have my home in git, and running git hub setup put the auth in > ~/.git/config. This prevented git hub clone from working, since I ran it > elsewhere and it didn't look at that config. Moving the auth token to > ~/.gitconfig worked. Suggest passing --global when setting this. > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages git-hub depends on: > ii git 1:2.5.0-1 > ii python 2.7.9-1 > > git-hub recommends no packages. > > git-hub suggests no packages. > > -- no debconf information > > -- > see shy jo -- Leandro Lucarella (Luca) https://llucax.com
signature.asc
Description: This is a digitally signed message part.
