`Merge` label when merge train is enabled is confusing usersne execution
Release notes
Problem to solve
While deciding on the scenarios for Auto-merge
, the team decided to go with just Merge
for when only merge train is enabled. So let's say if merge train is enabled, and a pipeline is in progress, users will see Set to auto-merge
but the moment the pipeline passes, the label changes top Merge
. Thsi change of label back an forth is giving users an impression that if the click on Merge
the change will be immediately merged, skipping merge train. Also because that's actually happening in a few situations, eg: #429516 (comment 1758618594) #439443
Intended users
User experience goal
User insight: When button label says Merge
users expect the MR to merge immediately
The label should accurately communicate the action to follow and should be in consistency with the language used else where in the product.
Proposal
Show Set to auto-merge
even when only merge train is enabled.
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
Feature Usage Metrics
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
What is the competitive advantage or differentiation for this feature?
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.