[go: up one dir, main page]
Skip to content

chore: Fix workspaces setup in GitLab UI

Enrique Alcántararequested to merge
fix-workspaces-setup into main

What does this MR do?

It fixes GitLab Workspaces setup in the GitLab UI project. The goal of this MR is encouraging the dogfooding of GitLab Workspaces by using this feature to contribute changes to GitLab UI. In detail, this MR contains the following changes:

  • Add initialization script to install asdf and yarn dependencies only if the environment is a Workpace.
  • Add documentation for using GitLab Workspaces
  • Update container image in devfile.yaml to use gitlab-build-images:workspaces-web-ide .
  • Update .vscode/tasks.json to set up an autolaunching task that executes the Workspace's initialization script.

How to test

Follow the steps in the documentation added int this MR.

Screenshots or screen recordings

The following video demonstrates how a Workspace auto-initializes the first time it is opened:

workspaces_gitlab_ui_720p.mov

Integration merge requests

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

  • Code review guidelines.
  • GitLab UI's contributing guidelines.
  • If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
  • If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
  • If the MR changes a component's API, integration MR(s) have been opened (see integration merge requests above).
  • Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • Label as security and @ mention @gitlab-com/gl-security/appsec
  • Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

  • All actions and functionality can be done with a keyboard.
  • Links, buttons, and controls have a visible focus state.
  • All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
  • Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
  • Color combinations have sufficient contrast.
Edited by Olena Horal-Koretska

Merge request reports