DrupalPod + Gitpod: Enabling Seamless Code Contribution

Are there any links to GitPod documentation?

Related Gitpod documentation -
https://www.gitpod.io/docs/configure/authentication/gitlab#connecting-yo...
and
https://www.gitpod.io/docs/configure/authentication/gitlab#registering-a...

I think this is now set up.

To sign into Gitpod, we needed to make an unprivileged account on GitLab.com since Gitpod requires social sign in, and should not be used with privileged accounts https://gitlab.com/DrupalAssociationGitpod

This is connected to git.drupalcode.org using another unprivileged account https://git.drupalcode.org/gitpod

@drumm, thank you for your help with this.

Opening any Drupal project hosted on git.drupalcode.org in Gitpod establishes Gitpod authorization for the user.

To test this, I opened the following URL in my browser:

https://gitpod.io/#https://git.drupalcode.org/project/drupalpod

I clicked on the "Authorize" link, which opened a new window where I authorized Gitpod. After authorizing and refreshing the original URL, I was able to open the project in Gitpod.

However, when I tried pushing code back to Drupal, I received an error. Looking at the Gitpod permissions in https://gitpod.io/user/integrations, it seems the missing "write_repository" is likely the cause.
(As the screenshot shows, Gitpod currently only showing "read_user" and "read_org" permissions enabled. It does not seem possible to enable even the "read_repository" permission at this time.)

@drumm, could you please add the write_repository? That is the original intent of this issue.

I'd expect GitPod to ask for write access when you click the authorize link, where you are taking personal responsibility for GitPod's secret handling and use.

The documentation at https://www.gitpod.io/docs/configure/authentication/gitlab#connecting-yo... says the service account access should be

Check the scopes api and read_user

Which is what was granted when authorizing the application.

As far as I know, this was set up according to the GitPod documentation. There may have been a change in GitLab or GitPod since the documentation was written. I think this would be a question for GitPod support.

@drumm I've been troubleshooting the issue with Gitpod team.

Their latest request is -

An admin of Drupal's GitLab instance needs to enable the read_repository scope for OAuth application in the GitLab preferences. After that you should be able to update it in https://gitpod.io/user/integrations without any errors.

Would that be possible to do?

That is now done, the Gitpod application for https://git.drupalcode.org/gitpod set up at https://git.drupalcode.org/oauth/applications/16 now has api, read_user & read_repository scopes.

Just tested this and I don't think it's working.

I used DrupalPod this moring to test a MR.
I checked my Git providers and git.drupalcode.org was set to api, read_user permissions.
I next deleted those permissions and logged out of Gitpod and D.O.

Following the steps in #5

1. Open https://gitpod.io/#https://git.drupalcode.org/project/drupalpod
2. Confirmed "Not Authorized" message.
3. Click "Authorize git.drupalcode.org"
4. Grant permission on popup
5. Gitpod no longer shows "Not Authorized" message.
6. Check "git.drupalcode.org" permssions on https://gitpod.io/user/integrations
7. Show "api, read_user"
8. Edit permissions to add "write_repository"
9. "write_respository" is _not_ available as an option.

Unlike #5, when I attempt to add read_repository permissions, I get an authorization popup.

Thank you @tyler36, I sent this information to Gitpod, and awaiting next steps.

In my experience, when I push code from Gitpod, I am getting a warning in VSCode that some permissions are missing, yet the code itself - does get pushed into Drupal's git (e.g. https://git.drupalcode.org/project/drupalpod/-/commit/f83588def03aaa6118...)