Motivation
github/gh-aw#56743 — Allow conclusion in on.workflow_run frontmatter schema, letting workflows filter which run conclusions (success/failure/etc.) trigger the agentic workflow.
Proposed test
- Workflow file:
test-copilot-workflow-run-conclusion.md
- Trigger:
on.workflow_run with a conclusion filter (e.g. success), plus workflow_dispatch as a secondary trigger so the harness can exercise it directly
- Engine: copilot
- Safe output:
create-issue
- Variant: standard
Minimal test prompt sketch
Configure on.workflow_run.conclusion: success watching a small upstream workflow (or itself), and on trigger have the agent create an issue confirming it fired only for the matching conclusion. Since the harness drives tests via workflow_dispatch, include a workflow_dispatch entry alongside workflow_run so e2e.sh can invoke it directly and assert compilation accepts the new conclusion field.
New fixtures or secrets needed
None — can reuse an existing lightweight workflow in this repo as the watched trigger source.
Notes
No existing test exercises on.workflow_run at all, so this also adds baseline coverage for that trigger type, not just the new conclusion field. Feasibility of full runtime exercise (actually observing a workflow_run completion) may be limited under --workflow-dispatch-only CI mode — worth confirming compile-only coverage is acceptable before promoting to a PR.
Generated by 🔍 Suggest New E2E Tests · auto · 27.6 AIC · ⌖ 1.9 AIC · ⊞ 8.3K · ◷
Motivation
github/gh-aw#56743 — Allow
conclusioninon.workflow_runfrontmatter schema, letting workflows filter which run conclusions (success/failure/etc.) trigger the agentic workflow.Proposed test
test-copilot-workflow-run-conclusion.mdon.workflow_runwith aconclusionfilter (e.g.success), plusworkflow_dispatchas a secondary trigger so the harness can exercise it directlycreate-issueMinimal test prompt sketch
Configure
on.workflow_run.conclusion: successwatching a small upstream workflow (or itself), and on trigger have the agent create an issue confirming it fired only for the matching conclusion. Since the harness drives tests viaworkflow_dispatch, include aworkflow_dispatchentry alongsideworkflow_runsoe2e.shcan invoke it directly and assert compilation accepts the newconclusionfield.New fixtures or secrets needed
None — can reuse an existing lightweight workflow in this repo as the watched trigger source.
Notes
No existing test exercises
on.workflow_runat all, so this also adds baseline coverage for that trigger type, not just the newconclusionfield. Feasibility of full runtime exercise (actually observing aworkflow_runcompletion) may be limited under--workflow-dispatch-onlyCI mode — worth confirming compile-only coverage is acceptable before promoting to a PR.