Can't push to public repository even though GitHub access is granted

[jankeromnes]

Describe the bug

I have previously granted write public repos to Gitpod in https://gitpod.io/access-control/:

But when I try to push to the public repository https://github.com/gitpod-io/website, I get this error:

gitpod /workspace/website $ git push origin jx/ruby-add-rails-sample-app 
remote: Invalid username or password.
fatal: Authentication failed for 'https://github.com/gitpod-io/website.git/'

When I click the GitHub audit link, Gitpod even seems to have "Full control of private repositories" (!) (I've granted it previously, but then revoked it, so this is surprising to me):

Note: Granting read/write private repos in Access Control does allow me to push to my public repository.

Steps to reproduce

0. Revoke read/write private repos in Access Control
1. Open a public repo (from an org maybe?)
2. Create a new branch
3. Try to git push origin new-branch

Expected behavior

Push should succeed.

Additional Information

Example Repository

[artalar]

Check this out #846 (comment)

[jankeromnes]

@artalar thanks! But my error message says:

fatal: Authentication failed for 'https://github.com/gitpod-io/website.git/'

I'm not using SSH authentication, so I don't think that's the problem.

[svenefftinge]

The fix/change is now deployed in production.

[Kreyren]

@svenefftinge Can you reference the relevant code which fixes the issue? It would help us to better understand how gitpod works for contribution

[JesterOrNot]

Sorry, @Kreyren AFAIK this is all in a closed sourced repository

[svenefftinge]

Yes, sorry, as Sean mentioned. The part that fixed it is closed sourced.
Please open an issue, if you still see this happening.

[MangelMaxime]

Hello,

Before the release of the fix I didn't have the error.

But now, I am seeing this error each time I am pushing to a repo even if the git push command is working. I am not sure how I can provide reproduction or more info about this problem.

[svenefftinge]

Please ignore the error message, as it is working otherwise. We have a fix that is going into production on Wednesday.