peterxcli commented on PR #11657: URL: https://github.com/apache/ozone/pull/11657#issuecomment-6312622771
@adoroszlai thanks for the explanation. This actually came out of my own needs. When a PR lags far behind upstream but everything looks good to go, I don't have the confidence to merge it without breaking the default branch, so I typically merge upstream and wait for a full CI rerun. With a merge queue, I could just hit "add to queue" whenever I think the patch is ready to merge. Furthermore, if the pull request CI is still running, I could enable auto-merge (add to queue) without any worry. Regarding the CI resource issue, I think we have a couple of options: 1. Pull request CI only runs unit tests, which are fast, and only the merge queue runs the full CI (UT, IT, smoke tests, ...). 2. The merge queue runs the full CI too, but pull request CI only checks the fork's CI status. Closing this now. I'm going to start a discussion thread on `dev@`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
