MR: Pending ## Description From @mvanremmerden > This is probably larger feedback than just for this single MR, but I'm not sure we already have specific plans for that, so using this place anyway: > > When we roll out the "Workspaces" part in the popover more widely, should we consider moving the Gitpod button to a "disabled by default" state? Right now we show it to every single user, no matter whether they have ever tried it out or toggled it on, and as we are getting closer to have a native feature built into the platform, we should probably be more considerate to not overload the UI with multiple options that all do roughly the same. > > Just as an example, if you look at the popover right now, we tell users that Gitpod is the right option if you want a "ready-to-code remote development environment" and Workspaces is the right option if you want a "virtual sandbox environment". I don't think it's clear to users what the difference between these two aspects is or why they should choose one over the other. ## Acceptance Criteria - Add a check on the backend to see if the GitPod integration is enabled for the user's group/project. - If it is not enabled, do not show the GitPod button in the Workspaces popover. - Remove any modals/tooltips referring specifically to GitPod as they will not be useful. ## Technical Requirements - Add a check on the backend to determine if GitPod integration is enabled for the user's group/project - Update frontend code to hide GitPod button if integration check returns false - Remove any GitPod-specific modals/tooltips from frontend - Update documentation around GitPod integration discoverability ## Design Requirements - https://gitlab-org.gitlab.io/gitlab-ui/?path=%2Fstory%2Fbase-button--default&args=disabled%3Atrue ## Impact Assessment - Users without GitPod enabled will have a cleaner interface without unnecessary buttons. - Discoverability of GitPod may be slightly reduced for some users. ## User Story As a user without GitPod enabled, I want the GitPod button hidden so that I have a cleaner interface without unnecessary clutter. ## Implementation guide The relevant component for this issue is [web_ide_link.vue](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/vue_shared/components/web_ide_link.vue). Follow these high level instructions to resolve this issue: 1. Only return a gitpod action if `gitpodEnabled` property is `true` in the following [function](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/assets/javascripts/vue_shared/components/web_ide_link.vue#L269). 2. Clean up all the code related to the "Enable gitpod modal". For example, the `gl-modal` component and the modal properties. 3. Remove the `userPreferencesGitpodPath` and `userProfileEnableGitpodPath` properties. 4. Update related tests and documentation.