Improve Verbiage When Trying to Create a Workspace from an Organization in GitHub

[jimmybrancaccio]

This was originally reported in a support ticket. I see we have some documentation in regards to this specific issue but I believe we have an opportunity here to improve the error message shown to the user when they try creating a workspace from a private repository in an organization.

Perhaps we can include a link to the above documentation or show the steps necessary to resolve this right within the error message. The error message shown to the user is:

Repository not found. (organization/repository) Your access token was updated recently. Please try again if the repository exists and Gitpod was approved for Organization.

I've replaced some of the text above - organization/repository, but the message is otherwise the same.

Front conversations

[kylos101]

@jimmybrancaccio can you share a set of steps on how to reproduce? For example, this could even be a link to open a Gitpod workspace resulting in the error you described.

[jimmybrancaccio]

@kylos101 The customer outlined this in their ticket (in my comment and their last reply). :)

Briefly:

Accounts were created in Gitpod first (using GitHub as their auth provider). An organization was then created in GitHub by a user that was different then the one whom opened the ticket. The reporting user however did join the organization. When the user tried opening a private repository from the organization it failed with the aforementioned error message. The user determined this was due to not giving the permission at https://github.com/settings/connections/applications/484069277e293e6d2a2a to the organization.

I recommend reviewing the ticket for further information.