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 LFS error reported after upgrading to latest Heroku CLI

See original GitHub issue

Description

I get this error when opening up Github Desktop, bad netrc file /Users/username/.netrc: line 7: keyword expected; got method. I believe it is not liking the entry in my .netrc file that is put there by the heroku CLI.

Here is what my .netrc file looks like with fake data:

machine api.heroku.com
  login fake@email.party
  password fake-password
  method sso
  org fakeorg

It looks like the Github Desktop is not liking this method line.

Version

GitHub Desktop: 1.1.1
Operating system: MacOS 10.13.4

Steps to Reproduce

Open desktop via the command line with github command
Error is displayed

Expected Behavior

No error during startup

Actual Behavior

Error displayed

Additional Information

Logs

2018-05-21T15:48:17.702Z - info: [main] Processing protocol url
2018-05-21T15:48:18.099Z - info: [ui] [AppStore] loading 12 repositories from store
2018-05-21T15:48:18.100Z - info: [ui] [AppStore] found account: codebender (Matthew Bender)
2018-05-21T15:48:18.686Z - info: [ui] launching: 1.1.1 (Mac OS 10.13.4)
2018-05-21T15:48:18.686Z - info: [ui] execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper.app/Contents/MacOS/GitHub Desktop Helper'
2018-05-21T15:48:18.727Z - error: [ui] `git lfs install --skip-repo` exited with an unexpected code: 2.
bad netrc file /Users/username/.netrc: line 7: keyword expected; got method

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:15 (5 by maintainers)

Top GitHub Comments

4reactions

ttaylorrcommented, May 29, 2018

@shiftkey I am looking at cutting a release containing that (+ a few other patches) for v2.4.2 early next week. Will that work OK for you?

Git LFS v2.4.2 was released containing https://github.com/git-lfs/git-lfs/pull/3027, which should fix this issue!

1reaction

shiftkeycommented, Jun 22, 2018

@codebender the fix is going out to beta now, with it slated to be available to everyone Monday

Top Results From Across the Web

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

"Not in a git repository" error in git-lfs - Stack Overflow

The directory must have a .git folder to be able to run git commands. To create one, run git init and then you...

Deploying with Git - Heroku Dev Center

Heroku doesn't support git lfs. Using this method can cause pushes to fail. Multiple Remotes and Environments. You can use the same techniques ......

Heroku error after update - Atlassian Community

I updated SourceTree and now the Terminal can not see Heroku. ... SourceTree opens GitBash and would run heroku cli commands until the...

Git LFS - CloudBees Documentation

Git LFS is not installed by default on CloudBees CodeShip Basic, ... Note, this script will automatically call git lfs fetch after installation....