We share our best practices to help every visitor to become a better dev.
Best Practices
It can be tedious and frustrating merging so many pull requests when you have a large open-source project and several developers working on it at once. All that merging takes up your valuable time. You have to review code yourself—or assign people to it—and rebase your branches periodically,
Technical
When you build an entire software around someone else API, you tend to know everything about it. We made Mergify [https://mergify.io] on top of GitHub API, and it's hard to describe how well we understand its API. From its fabulous and beloved features to its most
Basic Knowledge
If you're a video gamer and think you're not up to the task of launching a startup, think twice. At Mergify, we've been heavy video game players for the last couple of decades, and we think differently. Here's one thing we learned
Technical
A few months ago, we decided to build a referral program for Mergify [https://mergify.io]. This is a well-known, classical way of bringing more people on your product. To build this program, we add to define a data model that allowed us to store a list of referrers and
Best Practices
Running a project requires good security practice and management. Handling the security of software passes through holding the safety of its dependencies. GitHub's answers to that have been to provide a service named Dependabot [https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates] that sends security updates to your
Best Practices
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
Best Practices
Today, we're happy to announce a new feature that just landed in Mergify. You can now use the 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 of a pull request near
News, Events and Trends
You might have never noticed our accent, but Mergify is registered in the country where cheese is king: France. This has a myriad of implications and a pretty famous one among our peers selling digital services: companies registered in the European Union have to comply with the value-added tax for
Best Practices
While we all have a different way of managing our GitHub workflow, we all have to deal with one annoying thing: conflict. When a pull request modifies a file that has been modified in the meantime, GitHub shows you the famous Resolve conflicts button. This indicates the pull request cannot
Product Features
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
Best Practices
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.
Technical
GraphQL has seen a booming growth over the last years. A large number of API providers are switching to this new paradigm of querying data on the Web. At Mergify [https://mergify.io], we’re no exception. To implement our automation engine, we’re heavy users of the GitHub API