git bash doesn't use same credentials as GUI for Enterprise - problem for LFS
See original GitHub issueDescription
I stumbled upon this when trygin git-lfs. I use Github Desktop for most of my work, as we have quite a few people and students not familiar with git. To use lfs however, we need to use the bash.
I have a git version with bash installed, but that one doesn’t use the credentials as used by the GUI Github Desktop. This means that if I click “Open in bash” and try a simple git pull, I get an authentication error.
I am aware I can get around this by also configuring my other git installation to access both github.com and our own enterprise. It would be nice though to have a better solution so I don’t have to solve all authentication issues on our students’ computers.
Version
- GitHub Desktop: 1.5.1
- Operating system: Windows 10
Steps to Reproduce
- Install Github Desktop
- install git for Windows
- set up credentials for Github.com in Github Desktop
- Clone repository from Github Desktop
- Click on Repository > Open in git Bash
- try
git pull
Expected Behavior
Success
Actual Behavior
Following error:
remote: Invalid username or password.
fatal: Authentication failed for ‘https://github.xxxxx.xx/orgname/reponame.git/’
–
Additional Information
Logs
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:8 (6 by maintainers)
Top GitHub Comments
@JoFAM I’d love to hear more about what LFS actions you are doing that require dropping into the command line.
GitHub Desktop should support committing and push/pull/fetch operations for LFS-enabled repositories with the credentials stored in Desktop, but if there’s other tasks you are doing that aren’t possible within the app I’d love to ensure we’re aware of them and tracking them on our end.
Closing this out since as was mentioned GitHub Desktop does provide Git LFS support, and at this time we don’t have any plans integrate GitHub Desktop’s credentials with the command line.