Announcement of new products or features developed by Mergify.
Basic Knowledge
Most software projects are developed through collaboration—whether between a software team building a product or among individual developers creating an open-source project. Developers need a way to experiment with and isolate changes, such as new features, separate from the project. This makes it easy to track, discuss, and reverse
Product Features
From the beginning of our adventure, we built Mergify in the open. As we're building a tool for developers, we know how frustrating it can to work with closed software. In the continuity of our efforts and vision, we're launching today Mergify Discussions [https://github.com/
Product Features
Every day, we see more and more users joining Mergify. It turns out that, for the last couple of years, our growth has been fed by word of mouth. Many of our users started to use our service based on a recommendation of one of their fellows. Considering this, it
Best Practices
Requesting reviews on a pull request is a standard part of the workflow of most teams. However, there are a few subtleties to what may sound very basic. When assigning a pull request to a team rather than individuals, the pull request might get stuck forever. The diffusion of responsibility
Changelog
Another quarter of the year passed. It's time to reflect on what we achieved and delivered to our users during those last months. We won't cover various boring bug fixes — only the new and exciting features. Enhanced Branch Protection Support If you use protected branches [https:
Best Practices
Today, we're happy to announce a new feature that just landed in Mergify. You can now use the post_check action to post your custom checks into your pull requests. If you never heard of those, checks are statuses posted at the bottom of a pull request near
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
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