btw, all the bors permissions are now managed through the team repo!
so it's possible to easily assign whole teams to be reviewers, and permission changes do not require a central station redeploy anymore!
(adding repositories will still require a central station configuration change and redeploy, but permissions changes don't require that anymore)
@Pietro Albini if we used bors on a repo that is not rust-lang/rust, would it still participate in the bors queue?
I feel like that is undesirable
each repo has its own separate queue
particularly since landing a change in another repo doesn't directly affect rustc etc