Motivation
github/gh-aw#57816 — "Add native Linear Safe Outputs" merged upstream, introducing linear-create-issue, linear-add-comment, linear-update-issue safe outputs with credential isolation via linear-token. No test in gh-aw-test exercises this new integration.
Proposed test
- Workflow file:
test-copilot-linear-create-issue.md
- Trigger:
workflow_dispatch
- Engine: copilot
- Safe output:
linear-create-issue
- Variant: standard
Minimal test prompt sketch
Configure safe-outputs: { linear-create-issue: { team-id: ... } } with a samples: block so the test runs deterministically without needing a live Linear workspace. Prompt: "Emit a linear_create_issue safe output for a test issue."
New fixtures or secrets needed
Requires a LINEAR_API_KEY secret and a real/dedicated Linear team-id to validate beyond the samples: compile-time path — flagging as open question. Without live credentials, the test can only validate compilation + safe-output emission (via samples:), not the actual Linear API call, similar to how most create-* tests validate against this repo.
Notes
Since Linear is a new external system, first pass could validate only that the workflow compiles and the safe-output item is emitted correctly using --use-samples, deferring live-API validation until a Linear fixture/secret is provisioned.
Generated by 🔍 Suggest New E2E Tests · copilot · auto · 83.2 AIC · ⌖ 8.02 AIC · ⊞ 8.8K · ◷
Motivation
github/gh-aw#57816 — "Add native Linear Safe Outputs" merged upstream, introducing
linear-create-issue,linear-add-comment,linear-update-issuesafe outputs with credential isolation vialinear-token. No test ingh-aw-testexercises this new integration.Proposed test
test-copilot-linear-create-issue.mdworkflow_dispatchlinear-create-issueMinimal test prompt sketch
Configure
safe-outputs: { linear-create-issue: { team-id: ... } }with asamples:block so the test runs deterministically without needing a live Linear workspace. Prompt: "Emit a linear_create_issue safe output for a test issue."New fixtures or secrets needed
Requires a
LINEAR_API_KEYsecret and a real/dedicated Linear team-id to validate beyond thesamples:compile-time path — flagging as open question. Without live credentials, the test can only validate compilation + safe-output emission (viasamples:), not the actual Linear API call, similar to how mostcreate-*tests validate against this repo.Notes
Since Linear is a new external system, first pass could validate only that the workflow compiles and the safe-output item is emitted correctly using
--use-samples, deferring live-API validation until a Linear fixture/secret is provisioned.