Changelog
Another quarter passed, and it's now an excellent time to reflect on what changed for Mergify over the last three months. Multiple Queues One of our major projects over the last quarter is introducing the new queue action [https://docs.mergify.com/actions/queue/]. The queue action should
Basic Knowledge
A fundamental aspect of working on open-source projects is separating bug fixes, feature developments, and similar tasks into separate branches. Doing so lets developers experiment with code solutions free of the worry of messing things up in the main repository. However, these offshoot branches must be merged into the main
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,
Achievements
Today we're happy to announce the general availability of our new merge queues feature. This unique functionality allows engineering teams to secure their code merge by serializing them while parallelizing their testing. If your team never used a merge automation tool nor a merge queue, this is a
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
Versus
One of the most well-known and often-used git tools, the pull request is often also referred to as a merge request. These git-based requests are often utilized to promote cooperation and collaboration between software team members. They’re normally a required feature used by mid-sized or large teams. But what’
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
Product Features
A pull request [https://blog.mergify.com/what-is-a-pull-request/] allows a contributor to a project to experiment with new code changes without affecting the main project, then submit those changes for review. Managing pull requests can be time-consuming. You have to assign people to review code (or do it yourself), rebase
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
Tutorials
Try For Free
Basic Knowledge
Most software projects are developed through collaboration—whether between a software team building a product or among individual developers creating an open-source project. Developers need a way to experiment with and isolate changes, such as new features, separate from the project. This makes it easy to track, discuss, and reverse