Gitlab Workflow web view strategy
Problems to solve
GitLab Workflow has experimental features to allow users to view issue and MR details and comments in VS Code. These seem like beneficial features that we might want to make on by default. Before we pursue this we should develop a strategy on how we want to proceed from technical, UX, and product standpoints. This issue aims to establish a baseline for this.
Questions to answer
-
Why are these experimental, what is missing to make them production-ready? -
These are likely to require different UI elements from our design system, how do we want to handle this -
Are the current features acceptable? -
At a high level what types of this would we like to add to a merge request view inside VS code -
At a high level what types of this would we like to add to an issue view inside VS code
From extensions description
Experimental features are behind a feature flag. To enable them, you can set gitlab.enableExperimentalFeatures to true in your VS Code settings.
GitLab Workflow allows you to view issue details and comments right in the VS Code. Click an issue link from the sidebar and VS Code will open a new tab to show the issue details. You can also comment to the issue from VS Code. Currently, replying to discussions are not supported.
Updating assignees and labels are also not implemented. However, you can use GitLab Slash Commands to perform actions directly from VS Code. For example, to assign an issue to @username
, simply add a comment /assign @username
inside VS Code.