Skip to content

feat(ci): acknowledge rerun-test commands - #2676

Merged
guapisolo merged 3 commits into
mainfrom
jiajun/rerun-test-reaction
Aug 21, 2026
Merged

guapisolo merged 3 commits into
mainfrom
jiajun/rerun-test-reaction

Conversation

@guapisolo

@guapisolo guapisolo commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Summary

Acknowledge accepted /rerun-test commands and reply with the exact dispatched workflow run link.

Motivation

Accepted targeted-test requests need a direct path from the PR conversation to their Actions run. The PR feedback must confirm acceptance and identify the exact run without requiring a search through the Actions list.

Usage

Post /rerun-test tests/e2e/precision/test_hf_attention_cp_relayout.py. The original comment receives a +1 reaction, and the App posts a separate [View workflow run](https://github.com/radixark/miles/actions/runs/<run-id>) reply. The reply is not updated with later status changes; the final result remains in that Rerun Test run.

Design Notes

  • Mental model: The trusted command registry marks only RunTestFile for feedback; the Actions-scoped job reauthorizes the caller, dispatches the fixed default-branch workflow with return_run_details: true, validates the returned same-repository run ID plus URLs, then exports only that exact html_url; independent Issues-only jobs preserve the existing +1 acknowledgement plus post the link reply; label commands plus /rerun-failed-ci retain their existing routes.
  • SGLang at f1b9a1f4 establishes the reaction plus workflow-link reply model. Miles adopts those two signals but deliberately omits SGLang's later running/pass/fail comment edits.
  • GitHub's workflow dispatch API returns the run ID and URLs when return_run_details is true. The reply job never polls or executes PR code.
  • Feedback failures do not cancel or redispatch the accepted test run. An ambiguous reply response is not retried automatically; manually rerunning that job can create a duplicate link comment.

Verification

  • PYTHONDONTWRITEBYTECODE=1 python3 -m pytest -p no:cacheprovider tests/ci/test/test_comment_ci_command.py tests/ci/test/test_file_run.py -q: 227 passed, covering dispatch details, URL validation/output propagation, reply posting, preserved acknowledgement, and token/job isolation.
  • pre-commit run --files .github/workflows/comment-ci-command.yml .github/workflows/scripts/comment_ci_command.py docs/ci/01-label.md tests/ci/test/test_comment_ci_command.py: all affected-file checks passed.
  • Three independent read-only reviews found no P0, P1, or P2 issue.

Review Focus

  • GitHubAPI.create_workflow_dispatch: verify exact run-detail validation and no polling fallback.
  • acknowledge-command / reply-command: verify both feedback paths depend on successful dispatch and hold only Issues: write App tokens.

React with a thumbs-up only after GitHub accepts the targeted workflow
dispatch. Keep the reaction in a separate issues-scoped job so retrying a
failed acknowledgement cannot dispatch the test again.

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

Request workflow dispatch run details so the gateway can identify the exact Actions run. Keep the existing success reaction, and post the validated link from an independent Issues-scoped job so feedback failures cannot redispatch tests.
Replace migration-era wording with the current command, rollout, authorization, CUDA/ROCm, and fork-approval contracts. Keep the still-pending App setup and target-repository verification requirements.
@guapisolo
guapisolo merged commit 819ba96 into main Aug 21, 2026
24 checks passed
@guapisolo
guapisolo deleted the jiajun/rerun-test-reaction branch August 21, 2026 04:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants