 Do you often need to update a pull request before a merge so your changes won't break main? This is common in engineering teams that regularly merge into a busy branch. Well, I'm excited to share the pull request merge queues are now generally available. Before merge queues, you had to run continuous integration checks for each update. If another developer merged their changes, well, you had to start the process again and hope that you could finish your checks and merge your changes before anyone else. This created friction in your development process. But now the merge queue creates a temporary branch. This branch includes the source of the target branch, changes from pull requests ahead of you in the queue and your own pull request changes. Continuous integration runs once on this temporary branch and all required status checks must pass before your pull request can be merged. If the checks fail or there's a merge conflict, it's automatically removed from the queue. Plus, you can easily track your place in the queue and remove your pull request from the queue if needed. So are you ready to ship faster with less friction? Simplify your pull request process by using merge queues today.