Repository navigation
ci(pr-automation): explain skipped reviews - #1907
Conversation
Publish an Actions job summary when the automated review pipeline is skipped. List every gate and fork-quota blocker so maintainers can understand the decision without inspecting raw JSON logs. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
GitHub Actions
Inactive
There was a problem hiding this comment.
🟢 Approval recommended
The implementation is focused, consistent with existing automation, and adequately tested.
Pull request overview
Adds clear Actions summaries explaining why automated reviews were skipped.
Changes:
- Reports all failed review gates and quota blockers.
- Adds focused unit and workflow integration coverage.
- No material findings identified.
File summaries
| File | Description |
|---|---|
.github/workflows/labeler.yml |
Publishes the skip summary. |
.github/pr-automation/review-skip-summary.js |
Builds human-readable skip reasons. |
.github/pr-automation/automation.test.js |
Tests gate, quota, and workflow behavior. |
Review details
- Files reviewed: 3/3 changed files
- Comments generated: 0
- Review effort level: Balanced
github-actions
Bot
added
needs-review
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
Independent review of PR #1907: it adds a review-skip-summary module, unit tests, and a workflow block in resolve-review-state that publishes a job summary when the review pipeline is skipped. I verified the branching against the real producers: review-gate publishes gate.reason only on its catch path, fork-rate-limit emits limited/unavailable/allowed quota shapes, and resolve-review-state runs with always() so results are available even when the gate fails. Reason ordering matches the tested outputs, the fallback guarantees a non-empty list, and the state output is written before the summary block, so a summary failure cannot lose the state. Only minor, optional helper-extraction opportunities remain; no correctness, safety, or protocol issues were found. The skeptical reviewer timed out, so only the two code-compressor candidates exist; both are valid low-severity maintainability notes and are published (one with a corrected line range).
github-actions
Bot
added
ai-reviewed/1
…nnection-negotiation * upstream/master: (124 commits) feat(server): let an authenticated connection preempt an existing session (Devolutions#1476) ci(pr-automation): recover reviewer stages (Devolutions#1922) ci(pr-automation): report review check diagnostics (Devolutions#1926) ci(pr-automation): recover agent runtime (Devolutions#1921) ci(pr-automation): report reviewer recovery (Devolutions#1920) docs(pr-automation): define review recovery intent (Devolutions#1915) feat(web): expose enable_server_pointer from the WASM module (Devolutions#1914) fix(web): restore default remote cursor rendering (Devolutions#1910) feat(usb)!: support SuperSpeed packet sizes (Devolutions#1883) ci(pr-automation): explain reviewer ineligibility (Devolutions#1906) ci(pr-automation): explain skipped reviews (Devolutions#1907) ci(pr-automation): request JSON mode (Devolutions#1908) ci(pr-automation): repair empty agent responses (Devolutions#1905) ci(pr-automation): diagnose invalid repairs (Devolutions#1904) ci(pr-automation): simplify review findings (Devolutions#1901) fix(server): bound accept_finalize so a wedged client cannot hold the server (Devolutions#1890) ci(pr-automation): improve reviewer diagnostics (Devolutions#1898) ci(pr-automation): redispatch explicit retries (Devolutions#1897) test: focus PR automation workflow coverage (Devolutions#1896) feat(agent): add clipboard image support (Devolutions#1877) ... # Conflicts: # crates/ironrdp-server/src/server.rs
Publish an Actions job summary when the automated review pipeline is skipped. List every gate and fork-quota blocker so maintainers can understand the decision without inspecting raw JSON logs.
Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com