boa/bors.toml

# docs https://bors.tech/documentation/
status = [
	"Tests on Linux",
	"Tests on Windows",
	"Tests on MacOS",
	"Rustfmt",
	"Clippy",
	"Examples",
	"Documentation",
]
pr_status = [
	"Tests on Linux",
	"Tests on Windows",
	"Tests on MacOS",
	"Rustfmt",
	"Clippy",
	"Examples",
	"Documentation",
]
block_labels = [ "blocked" ]
required_approvals = 2
delete_merged_branches = true
use_squash_merge = true
update_base_for_deletes = true
Add bors to CI (#1684) This Pull Request updates some of our CI config and adds config for bors. It changes the following: - remove `cargo check` from CI (`cargo test` should be enough) - change back to `cargo tarpaulin` on Linux to get coverage information - simplify some of the CI steps' names - add workflow for bors ##### Working with bors It's setup so that we need 2 approvals before we can merge like we discussed in Discord. After the second approval we can write a comment with `bors r+` so that the merge is tested. bors will only run if `test`, `rustfmt`, `clippy`, `examples` and `doc` are all running error free in the PR's branch. It will then run them again in a `staging` branch that is the equivalent of merging the PR on `main`. Another option we can consider is `up_to_date_approvals`, so that new commits make previous approvals not count. The bors reference can be found here: https://bors.tech/documentation/ 3 years ago			`# docs https://bors.tech/documentation/`
			`status = [`
			`"Tests on Linux",`
			`"Tests on Windows",`
			`"Tests on MacOS",`
			`"Rustfmt",`
			`"Clippy",`
			`"Examples",`
			`"Documentation",`
			`]`
			`pr_status = [`
			`"Tests on Linux",`
			`"Tests on Windows",`
			`"Tests on MacOS",`
			`"Rustfmt",`
			`"Clippy",`
			`"Examples",`
			`"Documentation",`
			`]`
			`block_labels = [ "blocked" ]`
			`required_approvals = 2`
			`delete_merged_branches = true`
			`use_squash_merge = true`
			`update_base_for_deletes = true`