Best Practices
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
Achievements
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.
Product Features
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
Product Features
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
Best Practices
It’s no secret that Mergify is written in Python [https://python.org]. Our engine is open source [https://github.com/mergifyio] and is free for anyone to contribute to. That’s how we roll. We’ve been doing Python for a long time, and that got us close to
They Use Mergify
Mergify has been running for a few months now, and we thought it’d be cool to publish some discussion with our users. Reading about how developers leverage Mergify might be interesting for others and give good ideas to improve your workflow. Today, we’ll be talking with Sébastien Han,
Best Practices
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
Best Practices
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
Product Features
When you create a pull request in GitHub, you start building commits on top of a branch that is called the base branch. That new branch that contains your new code is called the head branch. Your goal is to merge the head branch into the base branch. The base
Achievements
Today’s the big day for Mergify! We’re starting our brand new engine, built from fantastic engineering skills and the feedback provided by our users. As we announced a few days ago [https://blog.mergify.io/a-sneak-peek-at-the-new-mergify/], we’ve transformed Mergify into a complete workflow framework for GitHub. You
Achievements
As I wrote a few weeks before, the Mergify team is working hard to bring new functionalities into the product. We conversed with many of our customers those last weeks and did our best to consolidate all the feedback we received into our roadmap. Now that we’re finalizing the
Achievements
The hot summer passed, and it’s now time to come back and cook some marvelous pull requests for your favorite projects!