Unexpected result/error message on forked project from private repo in different org

[stockholmux]

Bug description

I forked a private repo from an organization in Github. This organization has not granted GitPod permission for private repos. I have granted permission for GitPod to see private repos in my personal account.

When I try to get use gitpod on this private fork, I get the message Repository not found. / The repository 'stockholmux/<repo name>' is not found in your account. And it totally does! It took quite a while to understand what was going on.

I'm not sure if this is by-design and it makes some sense given the permission on the original organization, but the error message is really unhelpful.

Steps to reproduce

1. Create a private repo in an organization that hasn't granted permissions for Gitpod
2. Fork the private repo into your personal github account
3. Grant access for gitpod to your personal account
4. Attempt to access the forked repo via https://gitpod.io/#<repo url>
5. See the error message.

Workspace affected

No response

Expected behavior

Either gitpod can access the the forked private repo or show an error message similar to the origin repo which makes sense: (e.g.Repository not found. / Permission to access private repositories has been granted. If you are a member of '<org name>', please try to request access for Gitpod.)

Example repository

No response

Anything else?

No response

[axonasif]

I agree with you. I'm not sure but there can be some technical challenges here.

[stockholmux]

@axonasif To my knowledge this is also not documented as a known issue. It would be nice to have something to preserve my hair - that shouldn't be a technical challenge.

[axonasif]

that shouldn't be a technical challenge.

@stockholmux I meant that it could be a technical challenge to detect whether the private repo actually exists without having the necessary permissions granted beforehand. Sorry for not being clear enough 😅

[jldec]

Thank you for reporting this @stockholmux - we will investigate from the Gitpod side.

(I wonder if this may not be a bug on the GitHub api)

[jldec]

Scheduled.

A number of users have reported issues opening workspaces on private repos in the last week or so.
E.g https://discord.com/channels/816244985187008514/928500420966510702
cc: @axonasif

[jldec]

notes

1. Allowing forking of private repos is a (fairly recent) feature that needs to be enabled in the GitHub org settings, before a fork is even possible.
   

2. Granting third-party applications access to act on behalf of organization members (also in the org settings) is one way to get around the problem described above.
   

[stockholmux]

@jldec Yeah, note 2 is unlikely in my organization (bummer, but not a blocker) but the error message was my big issue.

[jldec]

pushing for a fix for this also in #8076 since there are issues working directly with private repos on orgs.