Backend: Add messaging when files can't be fetched due to invalid CI configuration
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
This is an issue add messaging when files can't be fetched due to an invalid CI configuration.
Proposal
Adding messaging similar to below to make it easy for a user to see the reason why a file isn't being used. This will allow a user to triage more quickly whether it's typed incorrectly or permissions are not set up properly and get their pipeline to green.
Reviewing if the request doesn't receive a mergedYaml, it could mean that something is wrong with the includes.
Implementation
The breakdown for this feature is as follows:
| Work Type | Description | Issue Link |
|---|---|---|
| backend | Expose includes link (initial MVC) | #344937 (closed) |
| frontend | Change the pipeline editor fixed layout to full-width | #346331 (closed) |
| frontend | Introduce the feature flag and the empty drawer. | #350721 (closed) |
| frontend | Pass down the content to the drawer and format it properly | #350722 (closed) |
| frontend | Remember the open/closed state in local storage | #350723 (closed) |
| frontend | Add feature discovery popover | #360111 (closed) |
| frontend | Roll out feature flag | #357219 (closed) |
| backend | Backend: Add toggle flag to UserCalloutFeatureNameEnum to allow for popover dismissal | #365347 |
| frontend | Store the pipeline editor popovers state in the database | #360635 |
| backend | Add messaging when files can't be fetched due to invalid CI configuration |
|
Edited by 🤖 GitLab Bot 🤖