Why does signing in with GitLab require full read/write API access?

There seems to be a huge discrepancy with signing in with GitLab vs signing in with GitHub, specifically with regard to permissions requested.

Signing in with GitHub wants nothing more than an email address (good):

<GitHub screenshot snipped due to restrictions on new users of posting only one media item>

But signing in with GitLab wants full read/write API access (whoa):

Something doesn’t seem right here… what’s up with this?

Thank you for reaching out. We are aware of the issue: https://github.com/gitpod-io/gitpod/issues/1932

1 Like

Thanks for the quick reply.

From what I gather, it seems like GitLab needs to do some work on how they handle permissions. I agree with Paul Slaughter’s assessment that this is a deterrent to user adoption (https://gitlab.com/gitlab-org/gitlab/-/issues/259254). I might look in to setting up a self-hosted Gitpod instance to integrate with my existing self-hosted GitLab instance so I can play around with it (I love FLOSS), but I am wary of using gitpod dot io with gitlab dot com (URLs spelled out due to limit of two links per post for new users) for the time being.