We share our best practices to help every visitor to become a better dev.
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
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