As organizations strive for CI/CD optimization, they often encounter various challenges along the way. One such obstacle is the merging of stacked pull requests. Stacked pull requests refer to the scenario where multiple pull requests are created and opened simultaneously, each dependent on the successful merge of its preceding
Best Practices
Discover a powerful CI tool combo for software teams relying on a CI/CD pipeline. Combine TeamCity and Mergify and you've got one of the best workflows around.
Technical
Continuous Integration/Continuous Deployment (CI/CD) is a crucial part of modern software development. CI/CD tools enable teams to automate the build, test, and deployment process, which is essential in improving software quality and accelerating the delivery of new features. Among the various CI/CD tools available in the
The rapid expansion of a project can lead to an exponential increase in the number of pull requests requiring processing. This surge in pull requests brings an inevitable, heightened demand for Continuous Integration (CI), leading to a consequent surge in both the time needed for CI and, subsequently, the associated
When working as a team during development, it's essential to use a standard set of guidelines for easy coordination and collaboration. Most engineering teams use Git to manage and version their software code. So, the development workflows are also mainly Git-based. Two of the most widely used workflows
Best Practices
Pull requests are vital for successful collaboration and continuous integration through GitHub or any other Git system. Developers use a pull request to ask the maintainer of the repository to merge the code into the project. A good pull request would have a better chance of immediate approval.
In today's fast-paced and highly competitive technology landscape, businesses rely on Continuous Integration to accelerate software development, enhance collaboration, and maintain high-quality codebases. While CI offers numerous benefits, it is essential to understand and manage the costs associated with its implementation and maintenance effectively. This article explores the
The main idea in a feature branch workflow is that development for each feature happens independently instead of in the main branch. That makes it easier for developers to work on different features without hindering or interfering with the main trunk. It also allows continuous integration since broken code never
Basic Knowledge
Handling large codebases is a tough job, and it's even harder when dealing with monorepos. A monorepo is a single code repository that contains multiple projects or modules. It's a handy way to share code across teams and manage dependencies. But dealing with monorepos can be
In today's fast-paced software development landscape, delivering high-quality software quickly and efficiently is more important than ever. To achieve this goal, teams need to measure and optimize their performance using metrics that provide actionable insights. The DORA metrics and the Accelerate book's four key metrics are
Best Practices
Try Mergify For Free
Changelog
We are pleased to announce the release of a new condition for our Merge Queue and merge automation, the Merge-After condition. Schedule Condition Limits While creating a general rule based on schedule condition was possible, it did not allow you to manage pull requests individually. - name: merge on working