This ticket represents the 2018 vision for ensuring stability of master, which is primarily achieved by adding the ability to validate the result of the merge to master *prior to* committing the merge, a feature that is not in the product today. - As a user when I merge a feature branch I want to make sure that master will remain green, since the impact of master being red is very high. - To be 100% sure it requires testing the merge of the feature with master, but master changes all the time and I'm not sure if I rebase that it will still be in sync. How the feature works: - Enable the ability to run build on merged code before merging (https://gitlab.com/gitlab-org/gitlab-ee/issues/7380) ### Customers https://na34.salesforce.com/00161000002xBfL ### Links/References - https://gitlab.com/gitlab-org/gitlab-ee/issues/3709 is the former meta issue tracking this overall deliverable. It has good historical information but should not be referred to as a current source of truth. There is also information there on potential future enhancements for release train in general. - https://gitlab.com/gitlab-org/gitlab-ce/issues/35261 is the product discovery issue, also containing good references for discussions at the time but not maintained as a current source of truth for this effort.