[Git] fatal: unable to access 'upstream': The requested URL returned error: 403

[jankeromnes]

Describe the bug

I'm unable to push to upstream, even though I should be able to.

(Pushing to origin works fine on Gitpod, and pushing to upstream from a non-Gitpod environment also works fine.)

To Reproduce

Open this pull request in Gitpod: https://gitpod.io/#https://github.com/mozilla/release-services/pull/1706

Then, try to push a commit to upstream/staging:

gitpod /workspace/services $ git remote -v
origin  https://github.com/jankeromnes/services.git (fetch)
origin  https://github.com/jankeromnes/services.git (push)
upstream        https://github.com/mozilla/release-services.git (fetch)
upstream        https://github.com/mozilla/release-services.git (push)

gitpod /workspace/services $ git push -f upstream "clean-up-after-before:staging"
remote: Permission to mozilla/release-services.git denied to jankeromnes.
fatal: unable to access 'https://github.com/mozilla/release-services.git/': The requested URL returned error: 403

As you can see, it fails with 403.

Expected behavior

Pushing to upstream/staging should work, just like in my local checkout:

(Note, I call Gitpod's upstream origin, and my personal fork jankeromnes instead of origin.)

jan@fox:/c/services (clean-up-after-before) $ git remote -v
jankeromnes	https://github.com/jankeromnes/services.git (fetch)
jankeromnes	https://github.com/jankeromnes/services.git (push)
origin	https://github.com/mozilla-releng/services (fetch)
origin	https://github.com/mozilla-releng/services (push)

jan@fox:/c/services (clean-up-after-before) $ git push origin "clean-up-after-before:staging"
Enumerating objects: 13, done.
Counting objects: 100% (13/13), done.
Delta compression using up to 8 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 629 bytes | 209.00 KiB/s, done.
Total 7 (delta 5), reused 0 (delta 0)
remote: Resolving deltas: 100% (5/5), completed with 5 local objects.
remote: This repository moved. Please use the new location:
remote:   https://github.com/mozilla/release-services.git
To https://github.com/mozilla-releng/services
   c20f2b1b..13487b42  clean-up-after-before -> staging

[AlexTugarev]

@jankeromnes, thank you for reporting this!

That's indeed confusing. Could you provide some more information on your member status at the github.com/mozilla organization? Are you a member/owner, or an outside collaborator?

In case you are an outside collaborator, you'd need to request permissions to use Gitpod with repositories of that organization. The request to use Gitpod can be done during the login with GitHub, or on the application's settings page. You would be able to push once an admin has confirmed that request.

All of that is part of GitHub's security model. The token issued by GitHub are meant to provide only the access necessary to do a certain task. Which means, we need to detect situations where you'd like to have write access to a repository, but your token cannot provide it. Good news: we've merged such a feature just recently on master. We'll need to improve the message to suggest requesting organizational approval for Gitpod.

[jankeromnes]

Hi Alex, thanks for your reply!

Could you provide some more information on your member status at the github.com/mozilla organization? Are you a member/owner, or an outside collaborator?

I'm a member of that organization:

Additionally, as a member of Mozilla's release-services team, I have "Write" access to https://github.com/mozilla/release-services/

However, I can confirm that Gitpod's OAuth application is not authorized by the mozilla org:

Which means, we need to detect situations where you'd like to have write access to a repository, but your token cannot provide it. Good news: we've merged such a feature just recently on master. We'll need to improve the message to suggest requesting organizational approval for Gitpod.

That's excellent news, thanks! Detecting such a situation, and offering a link to the application's settings page would indeed be very helpful.

[MangiringJosua]

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags --set-upstream origin master:master
remote: Permission to MangiringJosua/magangperpus.git denied to masrilpars.
fatal: unable to access 'https://github.com/MangiringJosua/magangperpus.git/': The requested URL returned error: 403
Pushing to https://github.com/MangiringJosua/magangperpus.git
Completed with errors, see above.

Cant you help me?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.