Improve merge train settings to match new merge strategy options
Release notes
Problem to solve
Based on the following decision in &7705 (comment 871768696)
In today's group meeting we all jointly decided for the incremental introduction of this feature starting with introduction of proper squash without merge commit followed by allowing more freedom of choice at time of merging. We also think we should introduce the first features with feature flags giving users a choice to try these out before this is fully implemented without forcing the incremental changes on all customers.
this issue would focus on the CI POV and develop a solution of the interaction of merge train and merge settings.
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
Metrics
Increased MAU for Merge trains
User experience goal
Based on the change in layout for the merge strategy and check in epic &7705, improve how we present the setting for merge trains in relation to other merge settings for a more intuitive configuration option for users.
Proposal
TBD - in workflowdesign
Further details
Permissions and Security
Documentation
Availability & Testing
Available Tier
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Yes, between groupcode review groupsource code and grouppipeline execution
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.