4 ms·
It's awful. I scrolled down to the how does it work section where the first sentence is: > Merge queue is designed for high-performance teams where multiple u
by jabradoodle 3y ago
It's awful.
I scrolled down to the how does it work section where the first sentence is:
> Merge queue is designed for high-performance teams where multiple users regularly commit to a single branch
Half of the how does it work section is buzzwordy fluff.
- hashar 3y agoThey don't need too since the link posted here is literally the press release announcement. For the inner details one should look at the documentation at https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue https://docs.github.com/en/repositories/configuring-branches... . It for example has a detailed example as how it handles a pull requests failing ahead in the queue https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue https://docs.github.com/en/repositories/configuring-branches...