### Problem to solve Enable the quick setup of CI/CD for new projects. ### Target audience <!--- For whom are we doing this? Include a [persona](https://design.gitlab.com/research/personas) listed below, if applicable, along with its [label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A), or define a specific company role, e.g. "Release Manager". Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply) - Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker - Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney - Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha - Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon - Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney --> ### Further details In order to entice additional usage of our CI/CD platform we should prompt users to `Setup CI/CD` one step earlier in the process. Right now the prompt exists once a file exists in the repository. We should also show it in empty repositories. ### Proposal Have this link:  Show up on this screen:  ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### What does success look like, and how can we measure that? Increased SMAU in Verify. ### Links / references