githubnext / githubnext/gh-aw-test
Suggested test: copilot/outcome-status-lifecycle
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
Link to the gh-aw PR or issue: github/gh-aw#46039 — add `OutcomeStatusLifecycle` and `OutcomeStatusLifecycleClose` as first-class outcome status constants
## Proposed test
- **Workflow file**: `test-copilot-outcome-status-lifecycle.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `add-comment` with `outcome-status: lifecycle`
- **Variant**: standard
## Minimal test prompt sketch
Instruct the agent to add a short comment to a designated test issue, then declare `outcome-status: lifecycle`. The harness asserts the workflow run outcome field equals `lifecycle`, verifying the compiler and runtime correctly propagate the new constant.
## New fixtures or secrets needed
None.
## Notes
Existing `test-copilot-report-incomplete.md` covers the `incomplete` outcome path. This test covers the two new lifecycle constants from PR #46039. All three engines should eventually be covered; start with copilot.
> [!WARNING]
>
> Firewall blocked 1 domain
>
> The following domain was blocked by the firewall during workflow execution:
>
> - `awmgmcpg`
>> To allow these domains, add them to the `network.allowed` list in your workflow frontmatter:
>
> ```yaml
> network:
> allowed:
> - defaults
> - "awmgmcpg"
> ```
>
> See [Network Configuration](https://github.github.com/gh-aw/reference/network/) for more information.
>
>
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/29569068059) · 26.7 AIC · ⌖ 5.61 AIC · ⊞ 5.6K · [◷](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
Start with the existing test-copilot-report-incomplete.md workflow and the proposed test-copilot-outcome-status-lifecycle.md file. Run the workflow with workflow_dispatch and verify that the copilot engine adds the designated comment and the harness reports outcome-status as lifecycle, without requiring new fixtures or secrets.
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
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 82/100