How We Do It
We explain how we work at Mergify, design, and develop our products.
Changelog Unleashed: Mergify's Leap into Automated Feature Announcements
In this blog post, we are diving into the process we created to generate our changelog, hence announcing our new features each time a pull request is merged.
Data Anonymization with PostgreSQL and SQLAlchemy
Developers face a unique challenge in the era of stringent data privacy laws like GDPR and SOC2 compliance. This article delves into how developers can access necessary data without compromising user privacy, specifically focusing on PostgreSQL databases.
Debugging Database performance issues in a snap with Datadog
Recently, our team experienced a breakthrough in database performance debugging, all thanks to Datadog's automatic explain queries feature. This powerful tool has saved us countless hours and significantly streamlined our debugging process.
Why Mergify's Codebase Isn't Open Source Anymore: A Tale of Growth, Change, and Adaptation
In 2018, when Mergify first saw the light of day, the world of software development looked rather different. It was a time when Mehdi, Mergify's co-founder, and CTO, and I aimed to alleviate the constant pain of rebasing pull requests for our team of just four developers. With
Password-less Authentication in 2023: Cloud Security with OpenID Connect
With growth comes a responsibility to ensure our operations' safety. This responsibility prompted us to delve deeper and rethink traditional security approaches, especially concerning cloud integration.
2023-07-31 Incident Postmortem
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
Engineering Growth: How Developers Can Master Marketing by Teaching
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
From Code to Community: The Evolution of Developer Advocacy at Mergify
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
Embracing Remote Work: How We Built Mergify as a Successful Asynchronous Company
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 merges
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
4 Reflexions on the design of the Merge Queue Freeze
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.
Handling unexpected third party API changes
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.