question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

git bash doesn't use same credentials as GUI for Enterprise - problem for LFS

See original GitHub issue

Description

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

  1. Install Github Desktop
  2. install git for Windows
  3. set up credentials for Github.com in Github Desktop
  4. Clone repository from Github Desktop
  5. Click on Repository > Open in git Bash
  6. 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

2019-01-16.desktop.production.log

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:8 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
shiftkeycommented, Jan 16, 2019

To use lfs however, we need to use the bash.

@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.

0reactions
stevewardcommented, Aug 1, 2022

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Git error: Encountered 7 file(s) that should have been pointers ...
I think the error was originally caused by files being checked in by a user NOT using Git LFS, then pulled down to...
Read more >
Git Large File Storage (LFS) - GitLab Docs
Git LFS client communicates with the GitLab server over HTTPS. It uses HTTP Basic Authentication to authorize client requests. After the request is...
Read more >
GUI Clients - Git SCM
Git comes with built-in GUI tools for committing (git-gui) and browsing (gitk), but there are several third-party tools for users looking for platform-specific ......
Read more >
a fast and friendly git client for Mac and Windows - Fork
Allow to merge images, LFS files and submodules in Fork merger. New. Intergration with Bitbucket server, GitHub Enterprise and GitLab Server.
Read more >
Deploying with Git - Heroku Dev Center
This article describes how to deploy code using Git and Heroku Git remotes. If you already track your code in GitHub, consider deploying ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found