Mergify

Mergify makes dev processes lightweight What do you like best about Mergify? Personally, I love automatic approvals. Our repositories need to be kept in sync, so we have robots opening PRs that bump dependency versions into specific files. It happens at least on a daily basis. We configured Mergify to automatically approve and merge the PR if CI remains green. We used to have people do it manually. It saves a bunch of time! What problems is Mergify solving and how is that benefiting you? Mozilla uses Mergify for some of our small to medium-sized projects, the largest being Firefox for Android. The source code of Firefox has historically been hosted outside of Github. Although 4 years ago, we decided to move the code of Firefox for Android to Github. Initially, we started with a startup mindset with very few processes. As the project gained momentum, we began to bring processes close to the ones we have on Firefox desktop. Mergify helped us to automate the last mile thanks to its merge queue, automatic approvals, and backports.

Mergify is one of, if not the most powerful automated merging services available right now. With their extensive configurability every scenario and idea that we've had to improve our code review & merging processes has been possible. Their customer support through their community Slack channel is incredibly fast and responding to questions which has made using Mergify a joy to use.

As we maintain multiple release branches, we save huge amounts of developer time with the ability to automate our backports to these branches. The devs only have to intervene when a backport fails. The only real issue is the infrequent downtime or slow response to github comments but those are becoming much more rare.

Currently the only versatile tool for managing PR queues for an always clean main branch. Mergify provides multiple queues to handle different types of priority for different PRs. This allows us to prioritize specific business-critical PRs so that our production stays healthy.