Mergify CEO & Co-Founder
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
Changelog
Happy New Year, everyone! We wish a brand new year full of development automation. 🦾 The year 2020 has been fascinating for us. We grew a lot. We saw a ton of new open source projects using Mergify to move faster. We had stimulating discussions with our users, and we will
Technical
Like many developers out there, you might use GitHub to store your source code. When you're building something pretty simple like a Web application, HTML files, JavaScript code, CSS stylesheets, etc., it could be useful to directly distribute your file through HTTP. The Naive Approach You probably tried
Product Features
From the beginning of our adventure, we built Mergify in the open. As we're building a tool for developers, we know how frustrating it can to work with closed software. In the continuity of our efforts and vision, we're launching today Mergify Discussions [https://github.com/
Product Features
Every day, we see more and more users joining Mergify. It turns out that, for the last couple of years, our growth has been fed by word of mouth. Many of our users started to use our service based on a recommendation of one of their fellows. Considering this, it
Best Practices
Requesting reviews on a pull request is a standard part of the workflow of most teams. However, there are a few subtleties to what may sound very basic. When assigning a pull request to a team rather than individuals, the pull request might get stuck forever. The diffusion of responsibility
Changelog
Another quarter of the year passed. It's time to reflect on what we achieved and delivered to our users during those last months. We won't cover various boring bug fixes — only the new and exciting features. Enhanced Branch Protection Support If you use protected branches [https:
Best Practices
Today, we're happy to announce a new feature that just landed in Mergify. You can now use the post_check action to post your custom checks into your pull requests. If you never heard of those, checks are statuses posted at the bottom of a pull request near
How We Do It
A few months ago, we blogged about how we handle our roadmap [https://blog.mergify.io/how-we-handle-our-roadmap-for-mergify/] at Mergify. The tool we mentioned using was Notion [https://notion.so], an all-in-one tool that can adapt to many usage. Notion is a useful tool, and we were able to adapt it
Best Practices
While we all have a different way of managing our GitHub workflow, we all have to deal with one annoying thing: conflict. When a pull request modifies a file that has been modified in the meantime, GitHub shows you the famous Resolve conflicts button. This indicates the pull request cannot