Frontend: Add pipeline editor to the split "Edit" button and make it the default option for .gitlab-ci.yml files
Release notes
Problem
Follow up from gitlab-org/ci-cd/pipeline-authoring#34 (closed)
Today the Web IDE is the primary option for editing .gitlab-ci.yml.
The pipeline editor is the primary solution for working with .gitlab-ci.yml file, we should make sure it is the primary action we present to our users when they want to edit their .gitlab-ci.yml.
Intended users
User experience goal
Make it easy to discover and use the best tool for editing a pipeline configuration in GitLab.
Proposal
Add the pipeline editor as an option to the split "edit" button and make it the primary option for editing .gitlab-ci.yml files.
Split button with the pipeline editor selected by default | Dropdown with options |
---|---|
![]() |
![]() |
- Pipeline editor should be the default option for editing for the .gitlab-ci.yml file.
- When the project has set up a different file in their project to be used as their main config, we should show the pipeline editor as the main option for that file. In other words, it should be the primary option for the project pipeline file, regardless of whether it's
.gitlab-ci.yml
or some other path. - We should remember the user's preferred editor. So if they switch to Web IDE, we need to remember that and show Web IDE as the editor next time they open the file view. It's the current split button behavior throughout the product.
Metrics
We could track the usage of the pipeline editor option against the other options when clicked into from the file view.
Is this a cross-stage feature?
Yes, it's a feature at the intersection of ~"group::editor" and grouppipeline authoring .
Links / references
Pipeline editor is the most used editor for pipeline config in GitLab, we want to make it more discoverable.