Do not fetch the pipeline status for brand new projects
Summary
When a user creates a new CI configuration file from the empty state of the pipeline editor, the app should not check for a pipeline status since there are no triggered pipelines yet.
This is a missed use case from #280829 (closed)
Steps to reproduce
- Open a blank project
- Go to the pipeline editor. You should be in the empty state.
- Clicking on the action button should lead to the editor.
- The app will keep checking for the status of the latest pipeline, which doesn't exist yet since it's a brand new project.
Example Project
https://staging.gitlab.com/mgandres1/blank-project/-/ci/editor
Note: The pipeline status is still disabled behind a feature flag and is not yet deployed to production.
What is the expected correct behavior?
For new projects, the pipeline status should be hidden until a new commit has been created (which creates the new pipeline).
The pipeline status component should also not be polling even while it's hidden.
Edited by Mireya Andres