General availability of GitHub\u2019s merge queue means good-bye to traffic jams on your team\u2019s busiest branches. No more rushing to merge your pull requests before someone else merges theirs \ud83e\udd75. Turn on GitHub\u2019s merge queue today and accelerate your merge velocity \ud83d\ude80.<\/p>\n
Any team that is part of a managed organization with public repositories and GitHub Enterprise Cloud users will be able to enable this feature on their respective repository and start streamlining their team\u2019s pull requests immediately. If this describes you, then let the commit parties commence \ud83c\udf89.<\/p>\n
Collaborative coding is powerful. But to be at your team\u2019s most optimized state, you need automated branch management that enables multiple developers to commit code on a daily basis, without frustration. This can happen if your team\u2019s branch is busy with many team members onboarding the same commit onramp. This can be frustrating for your team, but, more importantly, it gets in the way of shipping velocity.\u00a0 We don\u2019t want that journey for you!<\/p>\n
This is why we built merge queue. We\u2019ve reduced the tension between branch stability and velocity. Merge queue takes care of making sure your pull request is compatible with other changes ahead of it and alerting you if something goes wrong. The result: your team can focus on the good stuff\u2014write, submit, and commit.\u00a0 No tool sprawls here. This flow is still in the same place with the enablement of a modified merge button because GitHub remains your one-stop-shop for an integrated, enterprise-ready platform with the industry\u2019s best collaboration tools.<\/p>\n