Skip to content
GitLab
Next
    • Why GitLab
    • Pricing
    • Contact Sales
    • Explore
  • Why GitLab
  • Pricing
  • Contact Sales
  • Explore
  • Sign in
  • Get free trial
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #323374

Placement of editors on the project overview screen

Summary

After we introduced a "Open in VS Code" option in our "Clone" dropdown #220957 (closed), a discussion came up in Slack whether we should add the Gitpod button to that same dropdown.

leipert  1 hour ago
Wonder if the Gitpod button should live in the same modal :thinking_face:

leipert  1 hour ago
Maybe we could have a “Contribute” dropdown which includes:
- Web IDE, Clone, GitPod, Visual Code

Sid  1 hour ago
Since the web IDE already has a dropdown let’s add things under that?

phikai  1 hour ago
We put the VS Code action under clone - because it's much more similar to actions you need to take via cloning. The intent for the GitPod/Single File Editor/Web IDE is that they all live under a single Button.

phikai  1 hour ago
cc: @Eric Schurter who may have different thoughts about the Web IDE/SFE/GitPod

Eric Schurter  1 hour ago
I tend to agree that the more direct editing experiences that keep you within GitLab should be grouped, and this is more closely aligned with the action of cloning to your local machine. I’d support some lightweight user testing of this though, after we free up our design/UX bandwidth.

This would be similar to how GitHub handles their Codespaces option:

image

There also is a separate discussion happening around how to display the different Editor options on the Single File view: #296974

@mle @ericschurter Here is the issue I announced in Slack around the placement of Gitpod on our project overview page.

Assignee
Assign to
Time tracking