This article will take about 1 minute to read.
When you’re working on a project with other developers, at some point you’ll need to collaborate by merging contributions from multiple people into a single branch. Depending on how you end up doing this, you can run into different types of scaling issues, which may slow down your team’s velocity.
There are a couple of strategies for dealing with this that I’ll be going over in this post, namely
This is the merge strategy that most people are familiar with, and some large companies end up doing it too.
Merge Trains
https://github.blog/changelog/2021-10-27-pull-request-merge-queue-limited-beta/ https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/merging-a-pull-request-with-a-merge-queue#about-merge-queues