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
Product Features
When you are developing new products or features, time is key, and you can't accept being stopped several times because of malfunction. And by malfunction, we mean the main branch being red instead of green, with your developer team waiting and wasting time trying to repair the whole
In a team of software developers, the code reviews of your peers on your contribution to the code base are essential to build a product of great quality, while everyone keeps sharpening their skills in the process. Thanks to that, your team also stays aware of the evolution of the
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
Best Practices
Ever felt like CI is that overzealous friend who never lets you take a breather? You know, the one who insists on running a full marathon (read: functional tests) every time you want to go for a casual stroll (ahem, pull request)? Well, it's time to introduce this
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
Looking for the best tools to help you measure and improve code coverage? Check out our list of the top 12 code coverage tools for 2023.
Best Practices
Try Mergify For Free
Monorepos have become increasingly popular in recent years as they provide a centralized place for storing code for multiple projects or services. However, managing a monorepo can be challenging, especially when it comes to merging pull requests. This is where our merge queue and its partition rules feature come in