Mergify Reviews

Intuitive and easy to setup for various use cases.

Currently, I have yet to hit any major roadblocks personally.

If you're after an easy process to auto-merge and have a friendly bot to usher through your PRs to production, do not look past Mergify!

Mergify is streamlining our CI/CD process by making use of the auto-deployment features it provides us we simply just set up particular labels to coincide with the resultant deployment we're after;

ie. hotfix, releade_to_production/staging etc. These labels have been set up to give mergify the commands to handle our deployment and queueing of PRs. No longer do we manually have to usher through different PRs and keep an eye on the deployment process; now we trust mergify to handle those mundane tasks so we can focus on shipping.

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!

I don't see anything at the moment, actually. Mergify solves a specific need very well!

Don’t know why Mergify didn’t behave the way you expected? The extensive up-to-date report attached to your Pull Request is beneficial in debugging what is going on!

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.

The dashboard where I can evaluate my rules is great! Helps me set up the correct rules with immediate feedback and validation.

Furthermore, I'm impressed by Mergify's speed in reacting to PR changes. I add a label and Mergify takes action within a minute.

I wouldn't say I dislike anything. It does what it promises, and it does so well. But if I could wish for something, it would be more actions and more examples on how to use actions.

We use Mergify extensively to automate dependency upgrades. Recently we also set it up as a merge queue until GitHub releases a native merge queue. Great productivity boost because we need to spend less time on things that can be automated.

- Simple merge queue implementation

- In browser Config editor

Nothing as of now. Mergify works like a charm :)

Definitely go for it.

Mergify is a total changer for organizations having a large codebase. It does not just help you implement merge queues and supports many other features, such as PR automation.

Most definitely the automation is key here.

Nothing for now. I'll keep using it and suggesting feedback.

Try it out!

The highlight for me is how much time it saves me. Once you start using it, you would not have to worry about stale pull requests.

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.

There isn't really much I don't like about Mergify

Mergify provides a flexible and easy-to-use way to define PR merge queues, allowing a quality gate sanitizer of PRs before entering the main branch.

Since using Mergify, our main branch is always clear of faulty code.

It takes a lot of manual work off your plate and automates the most tedious tasks. It can even speed up your total PR volume with features like batch and speculative builds.

Branch updates could be automated (like once a day)

It automates the PR merge queue and is capable of parallelizing builds to speed up total merge volume.

Mergify helped me to reduce merge, rebase, and reviewer assignment time. It has become an essential part of my projects.

Merge queue and reviewers assignment are some of my favorite features.

So far nothing, it covers my use cases nicely.

My recommendation would be to give it a try, especially if you're working with more than 5 developers. It is really powerful and can make your git workflow efficient while keeping minimal configuration and saving engineering hours.

Mergify helps me to manage my open-source projects efficiently. It has cut down a lot of manual merging, rebasing, and review assignment time.

Mergify takes your complex workflow and simplify it by automation. When working on a lot of Pull Requests, on big projects and/or with large teams, there are always a lot of merge conflicts, merge trains to be respected (which can be very hard to do sometimes), and in general triage and management of PRs can be a nightmare. But with Mergify we could automate most of it, and the queue feature allows to have the merges taken care of cleanly and in the correct order.

Merge queues are definitely the biggest advantage of this tool. Yes, GitHub has merge queues as well (kinda), but what you can do with Mergify is tenfold... Especially having multiple queues on the same project. That is great.

THe only thing I'd like to see improved is having some sort of auto-completion in the rule editor, that would make Mergify even more user-friendly. But it is nitpicking.

Mergify helps in automating Pull Request management and Merges. This means the team leads and the devs have way more time to dedicate to coding, backlog grooming, and other important tasks. And this also minimize conflicts and issues!

Our CI pipeline takes over 90 minutes to run our test suite and before we had a merge queue our developers would waste so much time babysitting PRs. Mergify is easy to setup and customize and has allowed our team to scale while reducing the work needed from developers.

The docs are pretty good, but having more examples and use cases would be helpful.

We are reducing CI cost by about half while scaling the team. Also our developers don't need to use their time on merging PRs.