Mergify CEO & Co-Founder
Best Practices
GitHub Actions are a collection of tools that help you streamline your development workflows through automation. These actions are event-driven, meaning they’ll trigger upon certain things happening. There are tons of GitHub Actions you can use—here are some of the best. 1. Checkout Everybody knows about Checkout [https:
Product Features
Do you happen to know the common point between the open-source Node.js and Rust projects, the sporty social network Strava, the e-commerce company Shopify and the ride-hailing company Uber? Their engineering team all rely on a merge queue. Well, if you never heard of such a concept, you might
Best Practices
Once developers have completed work on project features and you’ve approved their pull requests [https://blog.mergify.com/what-is-a-pull-request/], it’s time to merge those requests into the main project repository. When doing so, Git has to find a base commit shared by two or more commits and then
Technical
We all knew it was going to happen anyway. GitHub just pulled the plug and removed Dependabot Preview. Dependabot was absorbed by GitHub 2 years ago now, and it seemed logical to phase out the Preview version of it. More than 30,000 organizations relied on this fabulous tool to
Best Practices
GitHub is a powerful tool for streamlining project collaboration among development teams. However, you can expand your capabilities even more by adding the right apps and tools to your GitHub repositories. With hundreds of apps available, though, which ones do you choose? Sifting through them all and keeping track of
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