bors — consistent automated testing | bors-ng

Bors is a GitHub bot that prevents merge skew / semantic merge conflicts, so when a developer checks out the main branch, they can expect all of the tests to pass out-of-the-box.

You open and review pull requests like normal on GitHub
When it's good-enough, instead of merging immediately, you tell bors to do it
Bors merges your pull request into a staging area, and runs your automated test suite
If staging passes, then it is copied to master

The cool part of separating the merging from the publishing is that the exact integration of pull requests that end up in master have already been tested before any developers try to work on it or users try to deploy it. It means less reverting commits after merging them, less hunting down others' mistakes before being able to do any of your own work, and, because bors does everything in the background, less waiting around for tests to run.

This September, bors was upgraded to Elixir 1.7

Running more than one GitHub app with the same name

This August, bugs affecting big repositories and delegation were fixed

This July, bors landed a fix that can help if the Installation webhook gets missed for some reason

This June, GitHub Reviews-related bugs got fixed

This May, I added support for gating on the new GitHub Checks API

This April, we added restricted retry and custom committer support

This March, we added support for gating Bors on GitHub Reviews

This February, we added some info to make things easier for self-hosters.

This January, we made bors-ng easier to deploy, hack on, and debug.

Older Newer