githubnext / githubnext/gh-aw-test
Suggested test: copilot/body-footer
- 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#60275 — Add additive global footers to safe-output bodies
Adds `safe-outputs.body-footer` (top-level, plus per-handler override) for appending shared content to every safe output that produces a body, supporting `{workflow_name}` and `{run_url}` placeholders, composing with imported-workflow footers and handler-specific footers.
## Proposed test
- **Workflow file**: `test-copilot-body-footer.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `create-issue`
- **Variant**: standard
## Minimal test prompt sketch
Configure top-level `safe-outputs.body-footer` with a distinguishing string (using `{workflow_name}` and `{run_url}` placeholders) alongside a `create-issue` safe output with its own handler-specific `body-footer`. Have the agent create a single test issue via `samples:`; assert the resulting issue body contains both the global and handler-specific footer text, separated by a blank line, in addition to the generated attribution footer.
## New fixtures or secrets needed
None.
## Notes
No existing test exercises `body-footer` composition. Distinct from `test-copilot-create-issue.md`, which only covers the base create-issue path without footer customization.
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/34683570501) · copilot · auto · 37.1 AIC · ⌖ 6.01 AIC · ⊞ 8.4K · [◷](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
Read test-copilot-create-issue.md for the existing create-issue test pattern, then add test-copilot-body-footer.md with a workflow_dispatch trigger and copilot engine. Configure global and handler-specific footers, create one issue through samples, and verify the body contains both placeholders-expanded footers, separated by a blank line, alongside the attribution footer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100