Expose GitHub-facing reruns for commit-status workflow reports

[gjkim42]

Context

Open Actions reports push, ordinary pull request, and merge-group workflows with GitHub commit statuses so the status target opens the Console run directly. Commit statuses do not provide the GitHub Check Run rerequest action, and Open Actions WorkflowRuns are not records returned by the GitHub Actions workflow-runs API.

The Console supports rerunning all jobs or the failed-job closure, but this leaves GitHub UI and CLI users without the rerun operation documented for GitHub Actions.

Goal

Provide a GitHub-facing rerun path for Open Actions workflow reports without losing direct Console links or weakening rerun authorization.

Acceptance criteria

• Support GitHub-facing requests to rerun all jobs and failed jobs for an Open Actions WorkflowRun.
• Define and either support or explicitly reject specific-job reruns.
• Preserve the original revision, ref, actor privileges, run identity, and incremented attempt semantics.
• Authenticate and authorize the requesting GitHub user and retain github.triggering_actor when an identity is available.
• Deduplicate retries without merging distinct user intents.
• Keep the commit-status target linked directly to the Console run.
• Add conformance and end-to-end coverage for GitHub UI/API/CLI-compatible behavior.
• Document supported operations and any explicit differences.

Reference: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs

[kelos-bot]

🤖 Kelos Task Status

Task open-actions-triage-issues-1ae0d0360a52 has succeeded. ✅

[kelos-bot]

🤖 Open Actions Agent @gjkim42

Open Actions Triage Report

Kind: kind/bug
Priority: priority/important-soon — Rerunning workflows is a documented, user-facing GitHub Actions operation, and this maintainer-opened gap removes a common recovery path from GitHub.
Actor: actor/human — A maintainer must choose the GitHub-side representation or bridge because Open Actions runs are absent from the GitHub Actions workflow-runs API, making UI/API/CLI compatibility an architectural product decision.

Status: STILL VALID

Evidence:

• GitHub documents full, failed-job, and specific-job reruns, repository write authorization, unchanged SHA/ref and original actor privileges, attempt history, and a 50-rerun limit. The workflow-runs REST API exposes separate full, failed-job, and job rerun endpoints for GitHub Actions run and job IDs. This is a documented compatibility gap, not an Open Actions-only feature.
• Current main still accepts authenticated check_run.rerequested deliveries, but its reconciler chooses failed jobs automatically for a failed run and all jobs otherwise. It does not expose distinct GitHub requests for all versus failed jobs or a specific job.
• Open PR #159 explicitly replaces eligible Check Runs with commit statuses, removes Check Run rerequest handling, and documents Console-only reruns. It does not fix Expose GitHub-facing reruns for commit-status workflow reports #160; it is the pending reporting change that makes the missing GitHub-facing path broader. No merged PR or recent matching commit references Expose GitHub-facing reruns for commit-status workflow reports #160.
• The current Console endpoint supports authenticated all-job and failed-job reruns, confirming that execution semantics exist but the requested GitHub UI/API/CLI entry point does not. The referenced CRD fields and workflow behavior remain present, so the report is not outdated.

Duplicates found: None found

Recommendation: KEEP OPEN — Decide the feasible GitHub-facing contract and its relationship to PR #159, then implement and document the supported subset and explicit incompatibilities.