rust-lang
Merge queue tracking issue
- [x] Add auto builds to PRs (#324)
- [x] Delete attached auto build and cancel running workflows on PR push (#326)
- [x] Add merge queue skeleton - we introduce the merge queue and refresh event (#350)
- [x] Add auto build creation, merge to base branch (#330)
- [x] Add tests for PR#326 (#383)
- [x] Update auto build docs (#385)
- [x] Improve auto build error handling (#386)
- [x] Reduce indentation and remove rightward drift (#405)
- [x] Deal with merge conflicts / non-fast-forward (#406)
- [x] Auto build startup failure (#410)
- [x] Sanity checks (#413)
- Mini-DSL for testing API?
- https://github.com/rust-lang/bors/pull/330#discussion_r2223128697
@Kobzol, if you have anything further to add, feel free to suggest else we're finished with this issue.
I think that you did most/all of what I described in https://github.com/rust-lang/bors/pull/386#issuecomment-3132390663. I think that we might want to have a few more tests, and maybe some DSL for that, but that's not urgent. I will take a look at the current implementation holistically, and try to test it on the kindergarten repo, and maybe add a few more tests.
In the meantime, if you want to continue forward, then I think you can either work on improving the queue page (https://github.com/rust-lang/bors/issues/371), implementing bors retry (https://github.com/rust-lang/bors/issues/319), or start thinking about rollups! Let me know on Zulip if you want to brainstorm how rollups could be handled.
I think we can close this, the base functionality is in. Thank you once again for this great work!