We explain how we work at Mergify, design, and develop our products.
In the dynamic landscape of software development, unforeseen challenges can occasionally arise, bringing with them valuable lessons and reinforcing the importance of collaboration. We'd like to provide an in-depth account of a recent incident that put these principles to the test. The Genesis of the Incident On July 31, 2023,
As engineers, we're programmed to think logically, to dive headfirst into complex problems, to find solutions, and, ultimately, to build. But when we transition from engineering to the thrilling world of startups, we find ourselves in unfamiliar territory, needing to acquire a new skill set — one that includes sales and
In the developer tools landscape, we carve our niche through a unique, bottom-up approach to marketing and developer advocacy. As the brainchild of two engineers, it seemed a natural course for us to target a demographic we knew so well—developers. Even as our marketing efforts have evolved to target
In a world where remote work is becoming increasingly popular, we at Mergify stand out as a prime example of a company that fully embraces the remote-first philosophy. Founded in 2018, before the COVID-19 pandemic, our roots are deeply ingrained in the world of open source and remote collaboration. In
Freezing your GitHub repository could mean a lot of things. In that case, I'm not talking about putting it on ice or sending it to GitHub's Artic Code Vault. No, that's not the point here. As controlling the merge flow becomes increasingly important, many engineering teams have encountered the need
Merge queues are at the center of the value offered by Mergify. The freeze feature we announced [https://blog.mergify.com/announcing-merge-queue-freezes/] a few days ago gives our merge queues a whole new range of possible use cases. You can now make your queues follow your product development life cycle.
As you may guess, Mergify relies a lot on third-party APIs like the Stripe API [https://stripe.com/docs/api] or the GitHub API [https://docs.github.com/en/rest] and their behavior. Like any third-party service, we need to deal with many things to ensure our integration never breaks.
Since its inception, the Mergify [https://mergify.com] engineering team decided to focus on its product and not spend time building infrastructure. It made a lot of sense as we started as a small team of two engineers with low resources and that the first version of Mergify was an
If this title does not ring a bell, you might need to read first what a merge queue is, what problem speculative checks solve, and how mixing speculative checks and batching can save you a lot of time. Go ahead. We'll wait. Now that you have an idea of what
Last month, we announced [https://blog.mergify.com/announcing-time-based-conditions/] a new set of conditions for Mergify rules based on time. You can now use a time and date and compare pull request attributes to dates and times. We had the idea for this feature since the beginning of Mergify, but
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 horrible defects,
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 playing video games. What's a Champion? Depending on