How starting merge trains improve efficiency for DevOps
Jan 30, 2020Orit Golowinski

Summary
This post introduces merge trains as a feature to order the flow of changes into the target branch, ensuring pipelines run on the latest version of the master branch. It details how merge trains work by queuing merge requests and running pipelines in parallel. The post also discusses the evolution of merge trains, including tuning concurrency, adding warnings for immediate merges, and supporting 'squash & merge'. Future plans include supporting fast-forward merges and API support for merge trains.