Frontend: Add a feature discovery popover to the pipeline editor file tree when a CI file in the project exists
Problem
In &7064 we're adding a pipeline editor file tree MVC feature. The file tree will be collapsed by default, and we need to add a prompt to surface it to the users who have a CI file already.
Proposal
When a project has a .gitlab-ci.yml file, when the file tree feature is released show a permanently dismissable feature discovery popover to promote the new feature. When the user navigates to the pipeline editor page after the feature release and they have a .gitlab-ci.yml file already (an indicator they're not as concerned with CI onboarding), we'll show the popover. The popover can be dismissed by clicking on "Got it" button, or by clicking/ focusing outside of the popover.
For detailed guidelines on the popover component usage see Pajamas: Popover.
For more context on the implementation see this thread.
 |
Implementation
The breakdown for this feature is as follows:
| Work Type | Description | Issue Link |
|---|---|---|
| backend | Expose includes link | #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 |
|
| 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 | #360431 |