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 the staging branch passes, then it is copied to the main branch

The cool part of separating the merging from the publishing is that the exact integration of pull requests that end up in the main branch 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 February, we fixed a bug when there's too many Co-Authored-By

This January, a config option for maximum batch sizes was added

Last December, the container was updated to Debian Bullseye

This November, bors's Gitpod and sync features were fixed

This October, bors underwent some internal maintenance

This September, bors landed a dependency bump

This August, we made several document improvements

This July, bors-ng became more robust to race conditions

This June, no notable changes were landed

This May, bors got an env variable for HTTP proxying

Older Newer