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 August, no notable changes were made to bors-ng

This July, bors-ng was upgraded to Elixir 1.12

This June, merge failures were changed to report on the PR

This May, bors-ng upgraded to the newest OTP, Elixir, and Phoenix version

This April, we added a couple features for self-hosters

This March, we added `bors cancel` as an alias for `r-`

This February, we added support for /CODEOWNERS path

This January, we added support for custom commit titles, and fixed a few CODEWONERS bugs

Last December, a few crashing bugs were fixed

This November, we added the `PUBLIC_PROTOCOL` configuration parameter

Older Newer