Rename MWPS to Auto-merge in Features
Why is this change being made?
As part of gitlab-org&6687 (closed) we've simplified the MWPS/MT/MTWPS text on the Merge
button to be Auto-merge
. This reflects a simpler language and enforces a single pattern regardless of the things that will happen when merging. This sets the stage for a broader Auto-merge
concept which would allow us to set things to merge when all requirements are satisfied instead of just the pipeline.
This change is active and in product, so this update reflects the required changes to features.yml
and to other places where the MWPS text/acronym was used in long-lived content.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Kai Armstrong