Clarifying how Gitpod workspaces work when opening Gitpod from GitLab UI
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=320937) </details> <!--IssueSummary end--> When you open a repository in Gitpod via the button in the GitLab UI, it always creates a **fresh, new workspace** in Gitpod for you. The mental model of what a Gitpod workspace is, and that you can run multiple next to each other, is something that requires a deeper understanding of Gitpod, that users with no experience of it might not have yet. I have had multiple calls with other team members where I needed to clarify that a **click on the "Gitpod" button will not bring up the same workspace they had started the day before**. Some of our users expected a more 1:1 relationship between GitLab repository and Gitpod workspace. GitHub Codespaces is a bit clearer in that regard, as they show you a list of all open workspaces for that repository next to the option of opening a new workspace: ![Codespaces](/uploads/09edbe63fbfe3fc295047e928452f046/Codespaces.mp4)
issue