Hi.
I just found that the roc source repository is now public. I would like to suggest that you implement bors as a merge bot. That would help with merge skew (see bors website) and make sure that development speed can be kept or increased without too much maintainers burden.
What do you think?
Thanks @Matthias Beyer, bors does look very useful, especially because github's new merge queue still has some problems. I'll look into adding it unless anyone objects.
I'm curious to see it in action. I was concerned about the comment trigger being manual, but I like that it correlates recent reviews into a combination matrix of sorts! Intriguing...
Yes, github merge queue is still not there yet. Bors works reasonably well, I'm using it in a few projects and am planning to introduce it to a bigger one. The rust project uses (AFAIK) a fork of it.
Please note that bors currently does an octopus merge if it can batch multiple PRs. There are issues on the bors repository that bors should also be able to do only one merge at a time. This can be enforced manually by commenting bors single on before bors merge, but there's no option to enforce it globally.
There is little development happening on bors lately, so it might take some time until this is implemented.
Last updated: Jun 16 2026 at 16:19 UTC