Change MR Pipeline feature names
Why is this change being made?
- Related to Proposal: Make "Merge request pipelines" the of... (gitlab-org/gitlab#350225 - closed)
- Resolves #12963 (closed)
As per the related issue, both internal and external users mostly use Merge request pipelines
and Merged results pipelines
as the feature names, and not many people use the "official" feature names of Pipelines for merge requests
and Pipelines for merged results
.
This MR (and the linked MRs for docs and UI) make it official that the feature name is the more common form. The handbook already uses this name mostly everywhere, and it aligns with the other pipeline types of "Scheduled pipelines", "Branch pipelines", "Tag pipelines", "Merge train pipelines", etc.
Other MRs
- MR For UI text - gitlab-org/gitlab!79224 (merged)
- MR for Docs - gitlab-org/gitlab!79197 (merged)
This MR also updates the docs links for Merge request pipelines, merged results pipelines, and merge train pipelines. Some only needed updates to the link text, some needed the link itself to be updated as well.
Approvals
Merge requests with changes to stages and groups and significant changes to categories need to be created, approved, and/or merged by each of the below:
-
VP, Product @david -
The Product Director relevant to the stage group(s) - @kencjohnston -
The Engineering Director relevant to the stage group(s) - @sgoldstein -
Director of Product Design @vkarnes -
CEO @sytses
The following people need to be on the merge request so they stay informed:
-
Chief Technology Officer @edjdev
-
Vice President of Development @clefelhocz1 -
Vice President of Quality @meks -
Vice President of User Experience @clenneville -
The Product Marketing Manager relevant to the stage group(s) - @supadhyaya -
Senior Manager, Technical Writing @susantacker
After Approvals and Merge
-
Create an issue in the triage-ops project to update GitLab Bot automation -
Mention the product group Technical Writer to update the documentation metadata -
Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels