Suggested test: copilot/custom-safe-outputs-zero-default-input
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Start with test-copilot-custom-safe-outputs.md to understand the existing custom safe-outputs job pattern, then use test-copilot-custom-safe-outputs-zero-default.md as the new workflow fixture. Exercise the workflow_dispatch path with the copilot engine and verify the numeric input remains 0 when unset, appears in the step summary, and causes failure if blank.
Written by the indexing model from the issue text.
Description
Motivation
github/gh-aw PR #58... "Preserve zero-valued input defaults" — fixed a bug where numeric default: 0 on custom safe-output job inputs was treated as missing due to truthiness-based fallback instead of nullish coalescing. No regression test exercises a numeric-zero default end-to-end.
Proposed test
- Workflow file:
test-copilot-custom-safe-outputs-zero-default.md - Trigger:
workflow_dispatch - Engine: copilot
- Safe output: custom
safe-outputs.jobs(similar to existingtest-copilot-custom-safe-outputs.md) - Variant: standard
Minimal test prompt sketch
Define a custom safe-output job with an input of type: number and default: 0, where the agent does not set the input explicitly. The job step should assert the received value is literally 0 (not empty/missing) and write it to the step summary, failing the job if the value is blank.
New fixtures or secrets needed
None — reuses the existing custom-safe-outputs job pattern.
Notes
Distinct from test-copilot-custom-safe-outputs.md (which uses a required string input, no default). Not present in fails.txt or open suggestions.
Generated by 🔍 Suggest New E2E Tests · copilot · auto · 41 AIC · ⌖ 12.2 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 ·