[UX] Fix - Link CI Onboarding MR Widget to the Pipeline Editor

Problem

When on the Merge Request page of a project with no pipelines, a user will see the option to add a pipeline through a "Show me how to create a pipeline" button. If the user hits merge first, then hits the pipelines button, the branch is deleted which causes the "Show me how to add a pipeline" button to lead to a 404.

Hypothesis

If we link the user to the Pipeline editor, the 404 error will not happen in the case of them hitting merge first.

Proposed Solution

  1. Adjust the link on the CI Onboarding MR Widget to go to the pipeline editor filled with a template and the drawer open with guidance on how to get started.
  2. Adjust the content on the CI Onboarding MR Widget to be the following:

Looks like there's no pipeline here.

GitLab CI/CD can automatically build, test, and deploy your application. It only takes a few minutes to get started, and we can help you create a pipeline configuration file.

Try out GitLab pipelines

Once they land in the pipeline editor, they can run their first pipeline immediately just by clicking the commit button since the template will already be prefilled. It won't set up a whole CI/CD workflow for them, but it'll run a test pipeline so the user can see how GitLab pipelines work.

Merge Request with No Pipeline Screen_Shot_2021-06-10_at_11.29.32_AM

**Pipeline Editor ** Screen_Shot_2021-06-10_at_11.29.39_AM

Measures of Success

TBD

Design File

Edited by Emily Bauman