Errors working with private repos on GitHub orgs, caused by missing 3rd party access for Gitpod

[jldec]

GitHub orgs now restrict 3rd party application access by default. This means that even after the Gitpod app is installed on the org E.g. when creating a /new project, 3rd party access to the org is not automatically granted to the Gitpod app.

Subsequent attempts to start a workspace on a private repo in the org will produce errors like: Repository not found with
Your access token was updated recently. Please try again if the repository exists and Gitpod was approved for <org>
or
Permission to access private repositories has been granted. If you are a member of <org>, please try to request access for Gitpod

Navigating to the Branches page on the new project, will show an empty branches list, and the browser console will contain an error message like
Getting branches failed Error: getProjectOverview failed with message: Although you appear to have the correct authorization credentials, the '<org>' organization has enabled OAuth App access restrictions, meaning that data access to third-parties is limited. For more information on these restrictions, including how to enable this app, visit https://docs.github.com/articles/restricting-access-to-your-organization-s-data/

Navigating to the Project Configuration page will show "No Access" Authorize github.com and grant repo permission to access project configuration, however, clicking on the "Authorize Provider" button will produce a spinning icon, and another console error
Uncaught (in promise) Erro: Request guessProjectConfiguration failed with message: NotFoundError

To approve 3rd party access for Gitpod on an org

A user who is an admin of the org, needs to approve the Gitpod app for 3rd party access to the org.

1. Go to https://github.com/settings/connections/applications/484069277e293e6d2a2a
2. Look for the org in queston in the lower section of the page under Organization access
3. Click on the Grant button .

[jldec]

Many users with private repos in orgs are hitting this issue. Treating as a bug because there is no visible indication in the UI for what is happening (console errors are hidden) and no links to instructions for how to fix.

Suggested improvements in Gitpod:

1. (If possible), when installing the app on the repository during /new, it should also enable 3rd party access.
2. The 2 start workspace error messages should be improved and point to (or include) instructions for how to fix.
3. Project Branches UI should not hide errors in console error logs.
4. Project Configuration authorization should detect this error state instead of spinning.

[jldec]

Correct 3rd party access

only the Gitpod app required below

Missing 3rd party access

[jldec]

This affects forks also.
#7482

[jldec]

Need visual design on showing errors for Project Branches and Project Config (currenty only in console)
cc: @gtsiolis

[jldec]

Another example from a support user (internal)