New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adopt bors #720
Comments
The recent github merge queue also looks like shares similar features about queue |
Ah, nice, even better. |
If somebody could check that our CI is compliant here, or prepare a PR otherwise, I can enable merge queues:
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue#triggering-merge-group-checks-with-github-actions
(I can't do this until later)
…On Sat, Mar 25, 2023, at 12:22 PM, Jeong, YunWon wrote:
The recent github merge queue also looks like shares similar features about queue
https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue
—
Reply to this email directly, view it on GitHub <#720 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABF4ZVYIGWQQOT7DKLEOLLW54LUDANCNFSM6AAAAAAWHPPT44>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I tested it with #733 and it works great. You will see |
@nikomatsakis I think merge queues are now enabled. I'm personally satisfied with it; do you think we should keep this issue open or we can close? Using GitHub's integrated solution has some obvious advantages. |
We should adopt https://bors.tech/!
The text was updated successfully, but these errors were encountered: