Before using Mergify, Glovo's engineering teams had two main issues.
First, many of their Github repositories receive contributions from hundreds of engineers regularly Every time a developer merges a pull request to the main branch, pull requests need to be updated and rebased to be retested. This creates a bottleneck as engineers need to maintain their pull requests for a long time.
Then, the mobile team uses Gitflow for development. This was not designed with continuous delivery in mind, and it's something that the team wanted to put in place.
That's why they started to look for a tool to automate and secure their merge, by keeping pull requests up-to-date as needed — speeding the merge time and reducing CI usage.
They compared multiple solutions and Mergify finally stood out.