Frontend: Editor shows an empty state when CI config is in another project
Problem
When the config is stored in a different project or outside of GitLab, we show an empty state in the pipeline editor that offers to create a pipeline config. It creates a broken experience for someone with an external config.
Documentation for setting up CI using a file in an external project:
https://docs.gitlab.com/ee/ci/pipelines/settings.html#specify-a-custom-cicd-configuration-file
Proposal
As an MVC, communicate that the config is stored outside of the project in the pipeline editor empty state. Adjust the empty state UI text and remove the CTA button.
This project's pipeline configuration is located outside this repository
To edit the pipeline configuration, you must go to the project or external site that hosts the file.
Edited by Mark Nuzzo