heroku login does not setup git credentials properly

[jakoss]

Reproduction pattern:

heroku login # i can login just fine, it passes, i'm logged in to proper account. I can use commands like heroku logs etc - i'm logged in properly
heroku git:remote -a myapp -r heroku-staging # this works, sets new remote with proper address
git push heroku-staging master # at this point i get the popup to provide git credentials

I tried to logout and login again, restarted machine multiple times - nothing helped.

Please help me diagnose and fix that

Additional info

This issue showed up after upgrading to v11.8.1

Machine: Macbook pro m4 (Tahoe 26.5.2)

[k80bowman]

@jakoss thank you for letting us know about this. Unfortunately I was unable to reproduce this, but as I'm investigating what's going on here, I have a question for you... Is it prompting for your username and password or only for your username?

In the meantime, if you run HEROKU_NETRC_WRITE=true heroku login the CLI will save your credentials in your .netrc file as it has done in the past (and not in your system keychain, as it started doing in v11.8.0) and hopefully your git push command will work as it used to.

[k80bowman]

internal work item

[jakoss]

@k80bowman thanks for quick reply. The prompt i'm talking about is that git credential popup that want's me to give both username and password. I can confirm that HEROKU_NETRC_WRITE=true heroku login did fix the issue for me :)

[ChipV223]

Hi @jakoss !

As luck would have it, I inadvertently was able to reproduce using the latest version of the CLI (currently heroku/11.10.0 darwin-arm64 node-v22.23.2) when investigating a different issue. Like you, I got the Git popup when executing git push heroku main, but I was able to resolve this by leaving the username as blank and passing in my Heroku API key via heroku auth:token as the password.

I'm going to try spin up a new environment to see if I get the same behavior and get back you with my results as they come!

[jakoss]

Hi @jakoss !

As luck would have it, I inadvertently was able to reproduce using the latest version of the CLI (currently heroku/11.10.0 darwin-arm64 node-v22.23.2) when investigating a different issue. Like you, I got the Git popup when executing git push heroku main, but I was able to resolve this by leaving the username as blank and passing in my Heroku API key via heroku auth:token as the password.

I'm going to try spin up a new environment to see if I get the same behavior and get back you with my results as they come!

Hi

I mean even if that works as a workaround - I'd still expect the heroku login to work out of the box without that 🙂

[ChipV223]

Hi @jakoss !

So I just tried this again on a different environment (Windows to be specific) and I wasn't able to reproduce the issue there (e.g. my git push was able to execute without the Git auth popup). What's more, I uninstalled and re-installed the CLI on my main Mac environment and I wasn't able to reproduce there as well.

Is it possible for you to install to the latest and greatest version and try to see if the issue occurs on your end (You would need to remove the HEROKU_NETRC_WRITE=true heroku login env to ensure a 1:1 test)

[jakoss]

@ChipV223 it does seem to be working now

[ChipV223]

@jakoss , that's good to hear.

I did try to reproduce in other environments and haven't been able to thus far. Since it's working with you now with the CLI upgrade, I'm incline to close this, but should it come up again, feel free to reopen the thread by adding a new comment!

[mars]

In our recent blog post about CLI's enhanced credential management:

When you log in with heroku login, set up your git remote using heroku git:remote, or create a new app with heroku apps:create the CLI will automatically configure the credential helper for your repository. Additionally, in order to ease the transition, for a limited amount of time any CLI command run will also configure the credential helper if it hasn’t already been set up.

It's possible that your git config did not get updated automatically or got reset… any future finders of this thread should check that their git config includes the git.heroku.com credential helper:

❯❯❯ git config list
…
credential.https://git.heroku.com.helper=!heroku git:credentials
…

If that's missing, then try adding it manually:

❯❯❯ git config --global 'credential.https://git.heroku.com.helper' '!heroku git:credentials'