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! Review collected by and hosted on G2.com.
I don't see anything at the moment, actually. Mergify solves a specific need very well! Review collected by and hosted on G2.com.
I think the best part of Mergify is the support, it is really great. Whenever we have had a feature request or a bug report, the issue or feature is often introduced/fixed rather quickly. Review collected by and hosted on G2.com.
My main gripe about Mergify is that is rather expensive. But the alternative is not much better either, as merging manually is not scalable when the number of PRs increases. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
Dashboard looks nice. It's relatively "fire and forget" once configured. Github does not have support for different MQ requirements on different tests. Review collected by and hosted on G2.com.
Mergify is hard to configure. It does not have a configuration for "wait for all tests to pass". Neither does github. Both claim that it is "impossible" to do this, but I think that's avoiding the point. It's clearly a painpoint that is solveable for the majority of use cases. For example, it could parse the .github/ directory.
When Mergify and/or Github actions fail, debugging the issue is difficult and requires currently specialized expertise. An advantage of avoiding mergify and using base tools from github is that anyone can debug. Review collected by and hosted on G2.com.
Merge queue (speculative checks). It's smart and it helps to reduce time to master Review collected by and hosted on G2.com.
Mergify is missing some configurability. Mainly the option to opt-out from branch protection rules. But it could have more options in general -> more options, more solutions it can solve Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
The only real issue is the infrequent downtime or slow response to github comments but those are becoming much more rare. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.
There isn't really much I don't like about Mergify Review collected by and hosted on G2.com.