Product Features
Announcement of new products or features developed by Mergify.
Announcing Datadog Integration
At the core of every new integration lies the needs of our clients; in this instance, they requested the integration of Mergify into Datadog. This may seem unusual at first, but there is a valid reason behind it. To effectively monitor and manage developer teams, it is crucial to have
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
Freezing your GitHub repository merges
Freezing your GitHub repository could mean a lot of things. In that case, I'm not talking about putting it on ice or sending it to GitHub's Artic Code Vault. No, that's not the point here. As controlling the merge flow becomes increasingly important, many engineering teams have encountered the need
4 Reflexions on the design of the Merge Queue Freeze
Merge queues are at the center of the value offered by Mergify. The freeze feature we announced [https://blog.mergify.com/announcing-merge-queue-freezes/] a few days ago gives our merge queues a whole new range of possible use cases. You can now make your queues follow your product development life cycle.
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
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
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
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
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
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
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
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.