bors — consistent automated testing

Automate the consolidation of git branches submitted by developers and test the merge results with your CI system (Travis CI, BuildBot, etc.) before commiting to the production master branch.

Running tests on each developer's branch is not sufficent. They may conflict in a semantic way that causes the master branch to fail when merged. Additional work that is built on such a broken master branch is tainted, unable to tell which failures are the result of an existing bug or a new one.

Instead, the combined system must be tested, as a whole, before the work becomes a part of the master branch which will form the basis of future work. Doing so, as work continues unabated, will force a backlog to be enqueued.

This system should be automated. The tool that automates this is called bors.

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.

This December, a few common sources of confusion were remedied.

This November, we added a permission mode for users who can "bors try" a PR but can't "bors r+" it

This October, a bunch of little usability improvements were made

This September, setting up your own instance got easier, the top-of-screen notifications got a close button, and more

What happened with bors in the month of August

There's a real, official place to ask questions now. It's at forum.bors.tech. You can log in with your GitHub account, just like you log into bors itself.

We screwed up and pushd a broken pull request into production

Older Newer

Fifteenth monthly bors newsletter Apr 1, 2018

Fourteenth monthly bors newsletter Mar 1, 2018

Thirteenth monthly bors newsletter Feb 1, 2018

Twelfth monthly bors newsletter Jan 1, 2018

Eleventh monthly bors newsletter Dec 1, 2017

Tenth monthly bors newsletter Nov 1, 2017

Ninth monthly bors newsletter Oct 1, 2017

Eighth monthly bors newsletter Sep 1, 2017

Get help using Bors-NG on the new support forum Aug 25, 2017

Downtime from 5:47 PM to 2:00 AM UTC the next day Aug 24, 2017