Prove that the dispatched workflow run finished with success. A completed run is not a successful run. The contract reads the conclusion of the run and an event that carries it.
| Fact | Value |
|---|---|
| Contract id | github.workflow_run.succeeded |
| Version | 1.0.0 |
| Hash | 310fe9de68836705 |
| Completion level | succeeded |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | GitHub REST API 0.1.0 |
| Valid for provider API versions | 2022-11-28 |
What is the intent?
Start the workflow on the reference and let it finish with success.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | github.workflow_run |
| Canonical effect | ci.workflow_run_start |
| Provider operation | POST /repos/{owner}/{repo}/actions/workflows/{workflow_id}/dispatches |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- other
- pre existing state
- wrong subject
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
github.openapi#/paths/~1repos~1{owner}~1{repo}~1actions~1workflows~1{workflow_id}~1dispatches/post: github.openapi, retrieved 2026-09-08github.openapi#/paths/~1repos~1{owner}~1{repo}~1actions~1workflows~1{workflow_id}~1dispatches/post/responses/200: github.openapi, retrieved 2026-09-08github.openapi#/components/schemas/workflow-run/properties/status: github.openapi, retrieved 2026-09-08github.openapi#/components/schemas/workflow-run/properties/conclusion: github.openapi, retrieved 2026-09-08github.docs.workflows#workflow-runs/dispatch-a-workflow: github.docs.workflows, retrieved 2026-09-08github.docs.workflows#workflow-runs/the-status-of-a-run: github.docs.workflows, retrieved 2026-09-08github.docs.workflows#workflow-runs/the-conclusion-of-a-run: github.docs.workflows, retrieved 2026-09-08github.openapi#/components/schemas/workflow-run/properties/head_branch: github.openapi, retrieved 2026-09-08github.openapi#/components/schemas/workflow-run/properties/created_at: github.openapi, retrieved 2026-09-08github.events#/events/workflow_run.completed: github.events, retrieved 2026-09-08github.docs.workflows#workflow-runs/events: github.docs.workflows, retrieved 2026-09-08
Can github.workflow_run.succeeded return VERIFIED from the action response alone?
No. The action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from GitHub REST API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.