Features

A collection of 31 posts

Features

What's a Merge Queue and why use it?

That's a good question, isn't it? Indeed, if it was only a little known term a few months ago, merge queues are more and more talked about. Between announcements from leaders like GitHub and real technical solutions, merge queues are increasingly adopted by software development teams. You will therefore dive

GitHub

How to Use GitHub Issues

Planning a project of any kind can be time-consuming. This is especially true in the development sphere, where details are often of critical importance. At a minimum, planning a project tends to involve setting objectives, defining timeframes, and specifying tasks to be performed. GitHub Issues accommodates these actions and more

Features

Announcing Merge Queue Freezes

Our merge queues have evolved along with Mergify. We've introduced more features to support more use cases. Today we are glad to introduce a new feature to expand even more possibilities. We designed a feature that allows engineering teams to freeze their merge queues to provide more control and security

Features

Speculative Checks and Batch: Under the Hood

If this title does not ring a bell, you might need to read first what a merge queue [https://blog.mergify.com/what-is-a-merge-queue/] is [https://blog.mergify.com/what-is-a-merge-queue/], what problem speculative checks [https://blog.mergify.com/announcing-speculative-merge-queues/] solve, and how mixing speculative checks and batching can save you a

Features

A Merge Queue on Steroids

In every engineering team, developers want to see their "ready to merge" work landing as soon as possible into their source code repository. Nobody wants to wait, and this directly impacts the velocity of the team. The worst part of the merging process would be to have to revert a

Features

Introducing Mergify API

Today, we are pleased to announce the general availability of the Mergify API. This has been one of our focuses over the last months, as it has been one of the most requested features from our beloved users. We are thrilled to release it and are eager to add more

Features

New draft and undraft actions

Pull requests are an essential part of the GitHub workflow. While they are mainly used as a way to merge your code into the base branch, it is not their only purpose. What if you wanted to create a prototype of a feature you would like to implement, just to

Features

Strict Mode Deprecation

When Mergify started to automate pull request merges, users expressed rapidly the need for having a way to keep their pull requests updated. We soon introduced the strict mode [https://docs.mergify.com/actions/merge/#strict-merge] for the merge action, offering pull request merge serialization. This was our first, very

Features

Behind the scene of time-based conditions

Last month, we announced [https://blog.mergify.com/announcing-time-based-conditions/] a new set of conditions for Mergify rules based on time. You can now use a time and date and compare pull request attributes to dates and times. We had the idea for this feature since the beginning of Mergify, but

Features

Announcing Time-based Conditions

Today, we're happy to announce the general availability of one of our most awaited features. Expressing conditions to act upon is the core of Mergify rules. While many dimensions are exposed through our configuration file and allow us to filter on many pull request attributes, one important was missing. Time.

Features

Announcing Boolean Operators in Conditions

Over the years, Mergify users wish they could be more expressive in the way they write their pull request rules. As those rules are a combination of conditions, being able to use or and and operators inside those expressions is a must-have. We are pleased to announce that this long-awaited

Features

Announcing Speculative Merge Queues

Today we're happy to announce the general availability of our new merge queues feature. This unique functionality allows engineering teams to secure their code merge by serializing them while parallelizing their testing. If your team never used a merge automation tool nor a merge queue, this is a crucial tool

Features

Introducing Referrals

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

Use Case

Randomly Request Reviews from Your Team

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

Mergify Changelog for 2020Q3

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://docs.github.com/en/

Features

Posting Custom Checks on Pull Requests

Today, we're happy to announce a new feature that just landed in Mergify. You can now use the post_check [https://docs.mergify.com/actions/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

Features

Selecting your Bot Account

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 problem. The Problem Mergify

Changelog

What's new in Mergify, 2020Q2

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 ago so

Features

Introducing Merge Queue Priorities

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

Features

Using templates in your messages

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

What’s New in Mergify, 2020Q1 Edition

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

Features

Improving the backport workflow

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

Changelog

What’s New in Mergify, 2019Q4 Edition

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

Changelog

What’s New in Mergify, 2019Q3 Edition

From now on, we’d like to share with you a summary of everything that happened during the last quarter of Mergify. This is a good way for you to get informed about new and exciting features, while a great exercise for us to reflect back on our progress! New

Features

New Pricing

We’ve been running Mergify for a few months now, hearing feedback from our users. Many of those reactions were related to bugs, features, that we spent time fixing and improving. Yet, we heard that there was one common issue that prevented organizations to adopt Mergify: our pricing model. It’