While tools like Github check for patch conflicts, they don't check for semantic conflicts (e.g. one PR adds a new use of a function another PR removes). This

While tools like Github check for patch conflicts, they don't check for semantic conflicts (e.g. one PR adds a new use of a function another PR removes). This is where merge queues come into play which have a variety of names (merge queue, submit queue, merge train, etc) I have a write up on merge queues [0] that goes into other benefits (e.g. speeding up PR builds), design considerations and their trade offs, and a comparison of various implementations. [0] https://epage.github.io/dev/submit-queue/ https://epage.github.io/dev/submit-queue/