-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Servo TSC Meeting June 2023 (2023-06-26) #66
Comments
I think it would be good to add an agenda item about linear git history / enforcing squash squash + rebase merge and experimenting with the GitHub merge queue. |
Possibly related to merge queue; I wonder maybe it's also worth considering making (corresponding API at https://docs.github.com/en/rest/actions/workflow-runs?apiVersion=2022-11-28#re-run-failed-jobs-from-a-workflow-run) |
My two cents on this topic: I believe linear git history is already implemented in bors https://github.com/servo/homu/blob/d6b918f45b4aadfb43ae4cba5b9b80a4f9c00638/cfg.sample.toml#L73-L74, not sure if it works though. Now about the merge queue, what would happen to our dear bors. I believe it would be pretty easy to make bors as an alias bot that dispatches merge queue events, to keep old workflow for those who were used to it and provide additional features like try/retry that merge queue does not offer. Rust-Lang is working on RIIR of bors that would be as lightweight as possible and I believe if we switch to GitHub merge queue it could be made as a stateless bot (with some stateful cache). |
Can this first be discussed on Zulip? I'm not sure if this needs to be discussed at the TSC per se |
FWIW I'll be a bit late (conflict) but I'm interested in this topic. |
Signed-off-by: Manuel Rego Casasnovas <[email protected]>
Signed-off-by: Manuel Rego Casasnovas <[email protected]>
Date
Monday 26th June 2023 at 15:00 UTC
Agenda
The text was updated successfully, but these errors were encountered: