<!--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=436599) </details> <!--IssueSummary end--> MR: Pending <!-- The first line of the MR must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, and the first description line of the MR should be `Issue: <Issue link with trailing +>` 3. `MR: No MR` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#1-to-1-relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description Context - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/140458#note_1707570053 * Create tables of all Remote Dev ENV vars we use, similar to https://docs.gitlab.com/ee/administration/environment_variables.html * The table for the user-facing `GITLAB_*` vars can live in user-facing docs, somewhere under https://docs.gitlab.com/ee/user/workspace/ * The table for internal `GL_*` vars can live in developer-facing docs * For now, this can be in https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/blob/main/README.md somewhere. * Going forward, I think we should create our own section for `Remote Development` under https://docs.gitlab.com/ee/development/feature_development.html#gitlab-components-and-features. This can initially just point to https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/blob/main/README.md, but we can eventually start migrating parts of that which make sense into the main docs repo. See also https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134984+, which involves refactoring and standardizing our handling of `GITLAB_*` ENV vars. ## 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 [If applicable, please list out any technical requirements for this feature/enhancement.] ## Design Requirements TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.] ## Impact Assessment TODO: Fill out or delete [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 [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.] <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->