githubnext / githubnext/gh-aw-test
Suggested test: copilot/enclave-github-tools-guard-policy
- 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#59816 — Fix invalid empty GitHub server guard policy for enclave-only GitHub tools
## Proposed test
- **Workflow file**: `test-copilot-enclave-github-tools-disabled.md`
- **Trigger**: `workflow_dispatch`
- **Engine**: copilot
- **Safe output**: `noop` (or `create-issue`) — the assertion is compile/runtime success, not the output itself
- **Variant**: standard
## Minimal test prompt sketch
Configure `tools.github: false` at the top level while scoping GitHub tools to an enclave agent, mirroring the bug's exact combination. Assert the workflow compiles and runs without the `mcpg` startup error `invalid server guard policy: ... min-integrity is required`, which previously occurred because the lockdown-detection step generator and its consumers disagreed on whether GitHub tools were enabled.
## New fixtures or secrets needed
None expected, but this depends on enclave-agent + scoped-tools frontmatter syntax not yet used in this repo's existing tests — needs confirmation of exact syntax during triage.
## Notes
No existing test combines `tools.github: false` with enclave-scoped GitHub tools. This is a narrow regression test for a compiler bug; scope should stay minimal (compile + boot success) rather than exercising a full enclave workflow.
> Generated by [🔍 Suggest New E2E Tests](https://github.com/githubnext/gh-aw-test/actions/runs/34456199311) · copilot · auto · 54.6 AIC · ⌖ 6.16 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
Start with test-copilot-enclave-github-tools-disabled.md and inspect existing enclave-agent and scoped-tools frontmatter in this repository to confirm the exact syntax. Add the narrow workflow_dispatch regression case with tools.github: false and enclave-scoped GitHub tools, then verify it compiles and boots without the mcpg invalid server guard policy error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100