CI linting involves a lot of manual steps
Problem to solve
Currently, users often have to navigate between the .GitLab-ci.yml
file and the CI lint view to test their CI configuration if using the Web UI.
Intended users
Further details
The problem of this issue has been validated with UX scorecard - Setting up GitLab-CI and can be reviewed with insight issue: https://gitlab.com/gitlab-org/uxr_insights/issues/832
Proposal
- Allow for CI linting to become available in the Web IDE.
- The Web IDE will feature a linting ability by adding a
lint
tab aside from theedit
tab as our MVC approach. - We need to make it possible to link directly to the lint tab of for example
.GitLab-ci.yml
- We'll then replace
ci/lint
with a link towards that as a follow up.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
Edited by Dimitrie Hoekstra