They Use Mergify
At Mergify, we want to show you that companies have different use of our software. Any workflow isn't the same! So for the very first time, we decided to launch a post series called #TheyUseMergify. Enjoy this first one 😁 They use Mergify: PyTorch Lightning Every day, major projects
Tutorials
GitHub has done quite a lot for the developer community over the years, facilitating the kind of collaboration on code that modern dev projects simply could not survive without. GitHub ships tens of thousands of improvements per year to help keep dev teams all over the world from waking up
Tutorials
It's not a secret that we are fans of Redis. We've been leveraging it since day one at Mergify to store various volatile data. It's fast, robust, and easily scalable. Six months ago, we introduced speculative checks [https://blog.mergify.com/announcing-speculative-merge-queues/] support for
They Use Mergify
When you work on software helping other software engineers, you end up having an excellent understanding of your craft. At Mergify, we talk to a dozen engineering teams every month, putting us in a pretty good position to understand their problems. This also gives us an average picture of what
Changelog
As security is everyone's priority at Mergify, we are thrilled to announce that Mergify is now SOC 2 Type II certified. This is a huge milestone for the team and a continuity in our commitment to maintaining a high level of trust with our partners, users, and customers.
How We Do It
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
Best Practices
Continuous integration, delivery, and deployment (CI/CD) offer software development teams a holistic means of meeting more milestones in less time. This is generally accomplished by simplifying complex and tedious, yet overwhelmingly redundant tasks through targeted automation. Once simplified, continuous integration, delivery, and deployment processes work to support development initiatives
Product Features
In every engineering team, developers want to see their "ready to merge" work landing as soon as possible into their source code repository. Nobody wants to wait, and this directly impacts the velocity of the team. The worst part of the merging process would be to have to
Best Practices
CI/CD tools can take your team to the next level of automated efficiency, effectively eliminating the need to manually test and review new features before they are merged with your main codebase and delivered to production environments. However, choosing the best option for your team takes careful planning. Below,
Product Features
Today, we are pleased to announce the general availability of the Mergify API. This has been one of our focuses over the last months, as it has been one of the most requested features from our beloved users. We are thrilled to release it and are eager to add more
Best Practices
As Mergify keeps growing, we keep encountering new issues. A few weeks ago, we explained how we had to adapt to our traffic increase [https://blog.mergify.io/handling-780k-github-events-per-day/] and handling close to 1M events per day. With growth comes its share of abusive accounts. In the same fashion that
Product Features
Pull requests are an essential part of the GitHub workflow. While they are mainly used as a way to merge your code into the base branch, it is not their only purpose. What if you wanted to create a prototype of a feature you would like to implement, just to