Update name of the VS Code fork injected into the workspace to avoid confusion with GitLab Web IDE
MR: Pending
Description
Update the name of the VS Code fork injected inside the workspace to avoid confusion with GitLab Web IDE
When running inside workspaces, call it GitLab VS Code fork as per the discussion in the below thread. This avoids confusion when users are reporting some issues(check screenshot) which are from workspaces but the screenshot would suggest that it is from GitLab Web IDE because that name is being used.
Acceptance Criteria
TODO: Fill out (required)
-
[Describe what must be achieved to complete this issue.] -
[Describe another requirement needed to complete this issue.] -
[Add additional acceptance criteria as needed.]
Technical Requirements
TODO: Fill out or delete (optional) [If applicable, please list out any technical requirements for this feature/enhancement.]
Design Requirements
TODO: Fill out or delete (optional) [If applicable, please provide a link to the design specifications for this feature/enhancement.]
Impact Assessment
TODO: Fill out or delete (optional) [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]
User Story
TODO: Fill out or delete (optional) [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]