Managing security updates on GitHub can get hectic in a hurry as third-party dependencies develop at their own pace, separate from your project. Leaving vulnerable dependencies unpatched can open your entire application up to otherwise avoidable threats, but manually reviewing and merging such updates can quickly eat up all of

A pull request allows a contributor to a project to experiment with new code changes without affecting the main project, then submit those changes for review. Managing pull requests can be time-consuming. You have to assign people to review code (or do it yourself), rebase your branches, and so on.

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

For the last few years, GitHub has supported a feature named CODEOWNERS. If you never heard of it, it’s a file that you can put in your repository, and that will make GitHub assigned pull request reviews to users or teams. CODEOWNERS 101Ok, so if you’re really new

Nowadays, there is a large number of online services that help you keep the dependencies list of your project up to date. Their goal is to make sure that you deploy your software with libraries and frameworks that do not suffer from major bugs and security flaws. Among them, you

A few weeks ago, a Mergify user came to us with the following problem: When a pull request is opened, we usually assign a few reviewers to it using GitHub user interface. What we’d like, is the pull request to be merged as soon as those reviewers approved the