Product Features
Announcement of new products or features developed by Mergify.
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
GitHub CODEOWNERS on steroids
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.
Improving your users’ onboarding: the case of Amazon CDK
As time passes, we keep seeing new and fancy ways of using Mergify to do other things than just merging pull requests. Today I’d like to dig into how Amazon Web Services Cloud Development Kit [https://github.com/aws/aws-cdk] project leverages Mergify to help its contributors. About AWS
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
Mergify definitely lands on the GitHub marketplace
Today’s a fantastic day for Mergify! We finally got verified by GitHub Marketplace team. That means you will now be able to subscribe to Mergify premium plans directly through GitHub. If you’re already a subscriber, nothing changes for you, and you’ll be able to stick to your
Mergify lands in the GitHub marketplace
We’ve been awaiting this moment for long, and here it is. As of today, Mergify is available directly from GitHub’s marketplace [https://github.com/marketplace/mergify]. That means you can directly setup Mergify from GitHub’s marketplace with a simple click. It does not change much the setup
Why You Should Not Fear Automated Merging
Mergify is soon going to celebrate its first anniversary. During that first year, we had tons of conversation with users. We received a lot of feedback from our users, which helped us to design our solution. As you know, one of the core features of Mergify [https://mergify.io] is
Now Is Time To Be Proud
This post will likely only resonate with our beloved users, but the time has come to celebrate! If you’re leveraging repository automation with Mergify, I’m sure you’re exultant about it. I mean, your life is easier, you’re merging, backporting, labeling with a blink of your eyes.
New Rebase Method with Strict Mode!
I know that title might sound a little bit obscure for developers that do not leverage Mergify. For our users however, it’s fantastic news! A few weeks ago, we’ve added a new configuration option to Mergify’s strict merge mode. If you don’t know what this strict
You Don’t Work Alone, so Mergify Supports Team
What’s software development without a team? Not a fun thing! A lot of our users are part of organizations, which means there are several people involved in developing software. Sometimes, organizations are large and creating teams helps to keep arrangement understandable. Therefore, GitHub supports creating team inside an organization
Merging Bots’ Pull Requests Automatically
Nowadays, there is a large number of online services that help you keep the dependencies list of your project up to date. Their goal is to make sure that you deploy your software with libraries and frameworks that do not suffer from major bugs and security flaws. Among them, you
Merging Pull Requests on Requested Reviewers Approvals
A few weeks ago, a Mergify user came to us with the following problem: > When a pull request is opened, we usually assign a few reviewers to it using GitHub user interface. What we’d like, is the pull request to be merged as soon as those reviewers approved