You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ env | grep GIT
GIT_CONFIG=/e/Dropbox/gitconfig
$ git config list --show-origin
file:E:/Dropbox/gitconfig alias.co=checkout
$ git config alias.co
checkout
$ git co
git: 'co' is not a git command. See 'git --help'.
$ git config alias.yo yooo
$ git yo
git: 'yo' is not a git command. See 'git --help'.
What did you expect to occur after running these commands?
I expected git checkout to run and then git yooo to be unrecognised.
What actually happened instead?
The alias failed to resolve and git rejected git co as an unrecognized command. git yo also failed to resolve to git yooo.
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
n/a
The text was updated successfully, but these errors were encountered:
If no --file option is provided to git config, use the file given by GIT_CONFIG as if it were provided via --file. This variable has no effect on other Git commands, and is mostly for historical compatibility; there is generally no reason to use it instead of the --file option.
In other words: This behavior of Git is by design, and it is not specific to Git for Windows.
Setup
defaults?
to the issue you're seeing?
Not that I know of.
Details
MINGW64 bash
Minimal, Complete, and Verifiable example
this will help us understand the issue.
I expected
git checkout
to run and thengit yooo
to be unrecognised.The alias failed to resolve and git rejected
git co
as an unrecognized command.git yo
also failed to resolve togit yooo
.URL to that repository to help us with testing?
n/a
The text was updated successfully, but these errors were encountered: