Best Practices
While we all have a different way of managing our GitHub workflow, we all have to deal with one annoying thing: conflict. When a pull request modifies a file that has been modified in the meantime, GitHub shows you the famous Resolve conflicts button. This indicates the pull request cannot
Product Features
New Mergify users might wonder what hides behind this cryptic title. Do not fear: I am sure you're going to like it. Before jumping into the feature presentation — which ought to be short as it's a simple variable in your configuration — you need to understand the
Changelog
Three more months have passed, and it's now time for us to share what we built and released over that time frame. Ready? Go! 📦 Batching! That might not sound that exciting, but trust us — it is. Mehdi wrote about it [https://blog.mergify.io/handling-300k-github-events-per-day/] a few days
How We Do It
As Mergify is a pull request automation tool, to execute actions on your pull requests, it needs to be aware of any change done on them. To get notified of any mutation, Mergify relies on the GitHub App webhook mechanism. That means that on any modification done to a pull
Achievements
Last year, GitHub announced the GitHub Sponsors program, a new way for organizations and individuals to contribute to open source. Today, we are glad to announce that you can contribute to Mergify using this program [https://github.com/sponsors/Mergifyio]. We've been providing a free service for thousands
Product Features
When you get hooked into automation, you always want more. For the last years, our users merged more and more pull requests using Mergify, leveraging our unique merge queue system. At some point, your queue so big that you need to organize it. This is especially true when your continuous
Product Features
As Mergify merges more and more pull requests for its users, new behaviors emerge, and new ideas come up. We’re building a tool for developers, and while we started by scratching our own itch, we’re now way beyond that territory — which makes it even more exciting if you
Changelog
As usual, this quarter has been a busy one for us. We still grow and helped many new users getting on board and automating their workflow. A lot of our effort this past quarter has been put in improving our engine and dashboard. Many of the changes we did are
Product Features
We spent quite a lot of time maintaining software in the past, with multiple stable branches. When a bug fix is committed in your development branch, you then need to copy it to your stable branches where the bug is present. This is why one of the first features we
Best Practices
For the last few years, GitHub has supported a feature named CODEOWNERS [https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners] . If you never heard of it, it’s a file that you can put in your repository, and that will make GitHub assigned pull request reviews to users or teams.
Changelog
This article is the second edition of our quarterly newsletter that summarizes everything that happened during the last quarter for Mergify. This quarter was a busy period for us. We continued our growth at a steady pace and brought a lot of new users on board. We’re merging thousands
How We Do It
Whatever you’re building — a company, a product, or a house — a time comes where you need planning. Pushing random buttons to move forward does not work anymore. You need to take a step back to think about what the optimal move to do next. This arrangement of your future