How to avoid broken master with Pipelines for merged results and Merge Train
Proposal
We recently introduced three killer features 1. Pipelines for merge requests 2. Pipelines for merged results 3. Merge Trains, however, the number of users who actively use these features are very low, today. We should advertise these features with explanations of when it's useful and how they can start using it.
Related https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/30661
Checklist
-
If you have a specific publish date in mind -
Include it in the issue title -
Give the issue a due date of a minimum of 2 working days prior
-
-
If time sensitive -
Added ~"priority" label -
Mentioned @rebecca
to give her a heads up ASAP
-