Display pipeline name on pipeline details and list pages
What does this MR do and why?
Describe in detail what your merge request does and why.
Display pipeline name on the list and details pages.
On the list page, the name will replace the commit title. If the pipeline does not have a name, the commit title will be displayed.
On the details page, the pipeline name will replace the commit title as the h3. The commit title will instead be displayed next to the commit SHA. If the pipeline does not have a name, the page will appear as it does now, with the commit title & description displayed at the top.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| With pipeline name | Without pipeline name | |
|---|---|---|
| Pipeline list page |  |
 |
| Pipeline details page |  |
 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- In your GDK, start a pipeline in a project. This pipeline won't have a name.
- Enable the feature flag by running the following in your Rails console:
Feature.enable(:pipeline_name). - Now, edit the
.gitlab-ci.yml, and add the following:workflow: name: 'Build pipeline' - Start a new pipeline. This pipeline should have a name.
- Visit the pipeline list and details pages.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.