How is Bors different from protected branches on Github?

Currently, I just have “require status checks” checkbox selected on my Github project. How is that different from Bors?

If you do not have the “Require branches to be up to date before merging” checkbox selected, then you are not implementing the NRSROSE (the Not-Rocket-Science Rule Of Software Engineering).

If you do have the “Require branches to be up to date before merging” checkbox selected, then you are implementing the NRSROSE. However, you are doing it much less efficiently than Bors does. You have to manually update a pull request with master, wait for the tests to pass, merge the pull request, update the next pull request with master, with for the tests to pass, merge it, update the next pull request with master, etc. Bors automates the entire process for you.

A more detailed explaination is available in the “But don’t GitHub’s Protected Branches already do this?” section of the bors-ng README.

Bors is not the only app that implements the NRSROSE. See this forum post for a list of other apps that also implement the NRSROSE.

1 Like

@notriddle Can we mark this thread as solved?

1 Like