Frontend: Add state when new commit doesn't trigger a pipeline in Pipeline Editor
When we make a new commit in the pipeline editor, we have a loading state while the pipeline is getting created. However, sometimes, the project configuration is so that no pipeline will run due to the configuration. Because the FE keeps waiting for the new pipeline, it will load forever, which is less than ideal as a UX.
Proposal
Expected user experience
When the pipeline doesn't trigger for the current commit based on valid configuration rules, we should show a message that explains it: No pipeline was triggered for the latest changes due to the current CI/CD configuration.
Implementation
The FE needs to know when no pipeline will be created due to project configuration. We could get this data back from the getPipelineHeader
query OR we could get that information back from the commit mutation. The second option seems cleaner to me, but I am curious to know what our backend engineers think.
Original issue: #346354 (comment 753152974)