Suggested test: copilot/linear-create-issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
Research direction
Create test-copilot-linear-create-issue.md with the specified workflow_dispatch trigger, copilot engine, linear-create-issue safe output, and samples block. Run the test with --use-samples; done means the workflow compiles and emits the expected safe-output item without requiring live Linear credentials.
Written by the indexing model from the issue text.
Description
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 · ◷
- Dominant language
- Shell
- Stars
- 8
- Forks
- 5
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-test
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-test#16875 ·
-
agentic-workflows suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-test#16262 ·
-
suggested new test
Difficulty 2/5 1-2 days Newbie friendliness 78/100
githubnext/gh-aw-test#15805 ·
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
githubnext/gh-aw-test#15094 ·
-
suggested new test
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-test#15092 ·
All issues in githubnext/gh-aw-test
Similar issues
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
chore
Difficulty 1/5 Under an hour Newbie friendliness 91/100
alunduil/alunduil-chezmoi#792 ·
-
area: compat bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
zenhub-dev
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenLiberty/ci.docker#747 ·