Prophesee × Mergify
How Mergify optimized Prophesee's development process while lightening the developers' mental load.
Outdated pull requests are at the root of many issues: rebase, code conflicts, broken main, and constant reverts… And developers' frustration.
Avoid them by using a merge queue: queue, rebase, and merge each PR automatically and sequentially.
Bye-bye, broken main, manual reverts, and rebases. Embrace velocity and make developers happy!
Open-source Node.js & Rust projects, the sporty social network Strava, the e-commerce company Shopify, Uber, etc.. Their engineering teams all rely on a merge queue.
To better understand what is a Merge Queue and its usefulness, let's imagine a GitHub repository in the following situation: a pull request is created, it passes the CI, and it is approved by reviewers. All the checks are green, just like the merge button.
1️⃣ Between the moment when all the checks are green and when you press the merge button, another one has just been merged and a new commit appears on the main. Not aware of that, you still see your PR as valid so you slap the merge button.
2️⃣ Boom, Code Conflict: you just broke the main branch! The outdated pull request you just merged introduces regression or breakages in the production system.
😭 Tons of engineers are confronted with this problem every day.
🦾 Using a merge queue solves that problem by updating any pull request that is not up-to-date with its base branch - thanks to an automatic rebase - before it is merged. The update forces the CI to retest the pull request with the new code from its base branch, catching any potential regression.
✅ Your Pull Requests are always up-to-date.
✅ Always test your PR before merging them.
✅ Ship and integrate only premium quality code to protect your Main Branch.
✅ Never break your production anymore.
Managing pull requests can be very demanding. You can relieve and enhance your engineering team by automating it with our merge queue.
Manage emergency pull requests by creating multiple merge queues based on priority!
.svg)
Discover how our Merge Queue can automate and streamline your dependencies updates with Dependabot.
By defining priority rules, you can define and custom a wide range of merge strategies, depending on the type of pull request.
Sometimes, a video says more than a thousand words. In this video.
Fabien will present you our Merge Queue solution thanks to a screen recording of the tool.
The change in developers' lives is amazing. When the code was broken, maybe half of the company was hunting the problem and looking for a solution. Now Mergify automatically finds the faulty PR and sends it back to the owner.
Senior Software Engineer
The configuration was helpful and reliable, so it was really easy. The only thing hard was to decide what to put in the configuration. Mergify removes work. Just use it!
Staff Engineer
Everyone is really happy that we got Mergify! It's a great success. It's reliable and stable. It does not cost much engineering effort to set up and it removed so much frustration while saving so much CI cost!
Head of Software Engineering
.png)
.svg){kind=icon}
