Best Practices

We share our best practices to help every visitor to become a better dev.

Hugo Escafit

The 7 Best CI/CD Tools in 2021

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,

Mathieu Papazian

How to Deal with the Abuse of your Service?

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

Julien Danjou

What Is a Git Merge Fast Forward?

Try For Free

Julien Danjou

The Best GitHub Productivity Tools

To get the most out of GitHub, it helps to choose the right tools. Developer productivity tools abound, but not all of them are worth adopting to improve your workflow. You can use the best productivity tools for programmers to enhance almost any part of your development process, including getting

Julien Danjou

Which Open Source License Should You Use for GitHub Project?

Choosing a distribution license for the software you publish on GitHub can seem confusing at first. After all, there are quite literally hundreds of licenses [https://spdx.org/licenses/] to choose from, all of which are suitable for different purposes and grant users of your code unique rights. For first-time

Julien Danjou

Code Review Best Practices

Adopting the right code review best practices can drastically speed up your review process while also improving the quality of your reviews. Often enough, code reviews can become areas of contention among members of your team, prompting them to become defensive about work they’ve done or changes they may

Julien Danjou

The Best GitHub Actions You Should Use

GitHub Actions are a collection of tools that help you streamline your development workflows through automation. These actions are event-driven, meaning they’ll trigger upon certain things happening. There are tons of GitHub Actions you can use—here are some of the best. 1. Checkout Everybody knows about Checkout [https:

Camille Clarret

The Essential GitHub CLI Commands

Last September, GitHub launched GitHub CLI 1.0 and brought GitHub to the terminal. GitHub CLI is GitHub command-line interface. It brings pull requests, issues, and other GitHub concepts to the terminal next to where you are already working with Git and your code — according to its documentation [https://cli.

Julien Danjou

What's the Best Git Merge Strategy?

Once developers have completed work on project features and you’ve approved their pull requests [https://blog.mergify.com/what-is-a-pull-request/], it’s time to merge those requests into the main project repository. When doing so, Git has to find a base commit shared by two or more commits and then

Julien Danjou

The Best GitHub Marketplace Apps You Should Use

GitHub is a powerful tool for streamlining project collaboration among development teams. However, you can expand your capabilities even more by adding the right apps and tools to your GitHub repositories. With hundreds of apps available, though, which ones do you choose? Sifting through them all and keeping track of

Julien Danjou

Everything You Need to Know About Git Merge

A fundamental aspect of working on open-source projects is separating bug fixes, feature developments, and similar tasks into separate branches. Doing so lets developers experiment with code solutions free of the worry of messing things up in the main repository. However, these offshoot branches must be merged into the main

Julien Danjou

Why You Should Be Using a Merge Bot in GitHub

It can be tedious and frustrating merging so many pull requests when you have a large open-source project and several developers working on it at once. All that merging takes up your valuable time. You have to review code yourself—or assign people to it—and rebase your branches periodically,