New Integration on Integrations page worded poorly for Self-Hosted installations

[lucasvaltl]

Bug description

Currently, on the integrations page it says: "Manage Git integrations for self-managed instances of GitLab, GitHub, or Bitbucket." - this makes it seem like this functionality is limited to self-managed SCM instances, and does not allow you to add public SCM provider instances (i.e. SaaS versions):

For a self-hosted installation this is confusing, because no integration for bitbucket.org, gitlab.com or github.com is set up by default. As such, you will also need to add the public/SaaS version of an SCM using the add integration mechanism, however this worded in a way that it seems like it only allows you to add self-hosted versions of the SCM providers:

As a comparison, see this screenshot on how it looks like on gitpod.io - where bitbucket.org, gitlab.com (SaaS version) and github.com are integrated by default and the wording makes more sense:

This is likely also linked to improving our integration docs for Self-Hosted users, which was discussed internally here.

Steps to reproduce

Spin up a self hosted instance, configure your fist git provider during the installation. Navigate to the integrations page in the dashboard.

Workspace affected

No response

Expected behavior

No response

Example repository

No response

Anything else?

No response

[jldec]

There appears to be some confusion about cluster-wide OAuth setup vs. registering private SCMs.

The git integrations section was indeed designed for non-admin users to add private integrations under their personal settings.

Configuring cluster-wide OAuth providers typically requires admin privs and happens at install time.
This is related to #9164.

[gtsiolis]

Cross-posting #10142 in case this could help resolve both issues. Cc @jldec @lucasvaltl

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.