githubnext / githubnext/gh-aw-test
Suggested test: copilot/user-rate-limit-frontmatter
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
Link to the gh-aw PR: github/gh-aw#56328 — "Fix user-rate-limit alias schema and event fallback"
`user-rate-limit` now accepts `max-runs-per-window`, `max-runs`, or `max` (deprecated aliases), rejects ambiguous configs specifying more than one max field, and falls back to all supported programmatic events when `events` is omitted and no trigger can be inferred. No existing test file references `user-rate-limit` frontmatter at all.
## Proposed test
- **Workflow file**: `test-copilot-user-rate-limit.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard
## Minimal test prompt sketch
Add a `user-rate-limit: { max-runs-per-window: 5, window: 60 }` block to frontmatter, compile, and have the agent create a simple confirmation issue. Primarily a compile-time/schema smoke test — the rate limit itself isn't triggered in a single dispatch run, but this confirms the field compiles and doesn't regress.
## New fixtures or secrets needed
None.
## Notes
Consider a second minimal case using the deprecated `max-runs` alias to confirm it still compiles (schema now permits it), though a single test covering the canonical field is a reasonable first step. No existing coverage exists for this frontmatter field.
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/33170338931) · copilot · auto · 22.6 AIC · ⌖ 3.81 AIC · ⊞ 8.8K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-test+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-test%2Fsuggest-new-e2e-tests%22&type=issues)
Contributor guide
No contributing guide indexed for this repository
Research direction
Create test-copilot-user-rate-limit.md using the specified workflow_dispatch trigger, copilot engine, standard variant, and create-issue output. Add the canonical user-rate-limit frontmatter block, compile the workflow, and confirm the agent creates the simple confirmation issue without requiring new fixtures or secrets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- markdown
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100