Strict Mode for your Continuous 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 comment bors r+, adding it to the merge queue
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 June, very little happened

This May, we fixed a few regressions

This April, we fixed a bunch of bugs in squash merging and approver counting

This March, bors was switched off of deprecated API endpoints and unsecure HTTP

This February, we added the `bors single on` command

This January, we added better error-handling and command parsing

Last December, several people helped clean up the squash merge functionality

This November, we fixed a few username-related bugs

This October, bors added squash-merge support

This September, we added CODEOWNERS file parsing to bors-ng itself

Older Newer