hello-stephen opened a new pull request, #66272:
URL: https://github.com/apache/doris/pull/66272
### What problem does this PR solve?
Issue Number: None
Related PR: None
Problem Summary:
A single `/review` comment currently expands into four serial jobs: resolve
PR metadata, mark the review pending, run the reusable review, and refresh the
required check. Three are lightweight orchestration, but each requests a
separate runner. Under runner pressure, every serial boundary can queue
independently, multiplying wall-clock delay before useful work starts.
This PR handles authorized `/review` comments directly in
`code-review-runner.yml`, resolves event or dispatch inputs in the first step
of the existing review job, and performs both status updates in that same
allocation. It preserves `workflow_dispatch` and `workflow_call`, the existing
authorization filter, and fail-safe status behavior. The obsolete four-job
dispatcher is removed.
One `/review` invocation now requests exactly one runner job instead of four
serial jobs.
### Release note
None
### Check List (For Author)
- Test:
- [x] Manual test
- `git diff --check origin/master...HEAD`
- actionlint passed for `code-review-runner.yml`
- YAML topology verified: all three supported triggers and exactly one job
(`code-review`)
- every embedded `run:` script passed `bash -n`
- issue-comment and workflow-dispatch input-resolution simulations passed,
including malformed API data failing closed
- success/failure final-status simulations passed
- Behavior changed:
- [x] Yes. A `/review` request now allocates one GitHub-hosted runner job
instead of four serial jobs.
- Does this need documentation?
- [x] No
A branch-scoped `workflow_dispatch` run will be attached after PR creation
to verify the exact head SHA, one-job topology, and terminal result.
--
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]
