Introduction
Informational RFC
Process RFC
0296 — Adopt a process for proposing, approving, and tracking major changes to bors-ng
0332 — Elixir and Erlang version update policy
0412 — Simplify bors-ng/bors-ng's label system
0434 — Show status on accepted RFCs
Feature RFC
0313 — The bors button extension
0322 — Pre-test and Pre-merge hooks
0347 — Ability to create merge commits locally in self-hosted instances of Bors
0349 — Use a squash merge in Bors
0357 — Bors support for CODEOWNERS
0360 — Add a new configuration option status_wait_success
0362 — Allow delegate to be abbreviated as d
0376 — Allow merge as an alias for r+
0388 — Wait for CI to finish instead of rejecting immediately on bors r+ when CI is still "pending"
0425 — Allow patches to be batched by themselves only
0471 — The required_approvals option should require up-to-date approvals
0507 — Update base branch of PRs depending on a branch that will be deleted
0508 — Log outgoing HTTP request
0521 — Add a new environment variable 'PUBLIC_PROTOCOL', to allow serving bors at a HTTP endpoint
0516 — Add support for custom commit titles
0547 — Make the database timeout configurable
0556 — Keep track of unmergeable and draft pull requests
0561 — Add "bors cancel" as alias for "bors r-"
0563 — Add a simple health check endpoint
0566 — Helm chart and examples using Terraform with Kubernetes
Light
Rust
Coal
Navy
Ayu
The Bors RFC Archive
Breaking backwards compatibility, or adding something new that will need to be kept working.