Motivation
Link to the gh-aw PR: github/gh-aw#52101 — Allow repository_dispatch user rate limits
user-rate-limit.events previously rejected repository_dispatch in its enum despite the compiler already treating it as an inferred programmatic trigger, causing valid frontmatter configs to fail compilation. This is a schema/validation fix with no existing regression test in this harness.
Proposed test
- Workflow file:
test-copilot-user-rate-limit-repository-dispatch.md
- Trigger:
repository_dispatch (custom event type) plus workflow_dispatch as a manual fallback trigger so the harness can exercise it
- Engine: copilot
- Safe output:
create-issue
- Variant: standard
Minimal test prompt sketch
Add frontmatter with on: { repository_dispatch: {}, workflow_dispatch: {} } and user-rate-limit: { max-runs-per-window: 1, events: [repository_dispatch] }. Confirm the workflow compiles successfully (this was the actual regression — compilation previously failed) and that a workflow_dispatch run still creates a sample issue reporting a static confirmation message.
New fixtures or secrets needed
None.
Notes
The primary regression here is at compile time (schema validation), so gh aw compile succeeding is itself most of the test's value; the runtime dispatch behavior of repository_dispatch itself is secondary and may need a follow-on manual trigger via gh api repos/.../dispatches if deeper runtime coverage is desired later.
Generated by 🔍 Suggest New E2E Tests · auto · 45.8 AIC · ⌖ 2.16 AIC · ⊞ 8.3K · ◷
Motivation
Link to the gh-aw PR: github/gh-aw#52101 — Allow repository_dispatch user rate limits
user-rate-limit.eventspreviously rejectedrepository_dispatchin its enum despite the compiler already treating it as an inferred programmatic trigger, causing valid frontmatter configs to fail compilation. This is a schema/validation fix with no existing regression test in this harness.Proposed test
test-copilot-user-rate-limit-repository-dispatch.mdrepository_dispatch(custom event type) plusworkflow_dispatchas a manual fallback trigger so the harness can exercise itcreate-issueMinimal test prompt sketch
Add frontmatter with
on: { repository_dispatch: {}, workflow_dispatch: {} }anduser-rate-limit: { max-runs-per-window: 1, events: [repository_dispatch] }. Confirm the workflow compiles successfully (this was the actual regression — compilation previously failed) and that aworkflow_dispatchrun still creates a sample issue reporting a static confirmation message.New fixtures or secrets needed
None.
Notes
The primary regression here is at compile time (schema validation), so
gh aw compilesucceeding is itself most of the test's value; the runtime dispatch behavior ofrepository_dispatchitself is secondary and may need a follow-on manual trigger viagh api repos/.../dispatchesif deeper runtime coverage is desired later.