If you're unfamiliar with Bors, check out this post for a short primer.
You will also need to sign up for app.bors.tech to follow along here. Do this and give the Bors service permission to access at least the repo you're using to test with.
Here's a GitHub Action that uses nightly Rust to run
cargo check. There are two important parts of this workflow.
trying. We never push to these branches manually. We only submit PRs.
Borsbecause I only have one that I care about, but you can have many.
Secondarily, we need a
bors.toml in the root of our project. This toml file will include any config we want to use. In this case, it specifies which Job statuses to pay attention to for merging purposes. We've specified the name here that matches the job we care about in our GitHub Action above.
That's it, now you can
bors r+ to your heart's content.
If you're working in the JS ecosystem, you'll want to pair the Bors workflow with Changesets to manage npm semver releases via PR as well.