Feature Idea
Summary: Update scripts/quick-setup.sh so users can still paste COPILOT_GITHUB_TOKEN when running the documented curl ... | bash setup flow.
Why a Customer Would Want This
The default onboarding path is a piped command, but token entry currently requires terminal stdin. First-time adopters can hit a hard failure unless they already know to pre-set COPILOT_GITHUB_TOKEN or use --skip-secret, which adds friction at exactly the moment setup should be easiest.
Rough Implementation Sketch
- Add a small token-input helper in
scripts/quick-setup.sh that reads from /dev/tty when stdin is non-interactive but a terminal is available.
- Keep existing behavior unchanged for current successful paths (env var set,
--skip-secret, and dry-run).
- Update quick-start docs to note that piped execution supports interactive token prompt fallback.
- Add/adjust a lightweight script test path for non-TTY stdin behavior if existing shell tests cover this script.
Why It Won't Be That Hard
This is a tightly scoped shell-script change in one code path (token acquisition) with no workflow schema/compiler impact and no behavior changes to existing successful setup flows.
Evidence
- Piped install is the documented default quick-start path:
docs/index.md lines 62-67 and README.md lines 32-35.
- Docs say this flow sets
COPILOT_GITHUB_TOKEN: docs/index.md lines 69-74.
- Current code only prompts for token when stdin is a TTY (
[ -t 0 ]), otherwise exits with an error: scripts/quick-setup.sh lines 225-245.
- No open duplicate found for this exact gap via issue searches:
repo:elastic/ai-github-actions is:issue is:open "stdin is not a terminal" quick-setuprepo:elastic/ai-github-actions is:issue is:open quick-setup token promptrepo:elastic/ai-github-actions is:issue is:open quick-setup --skip-secret COPILOT_GITHUB_TOKEN
- Prior PM issues tracked in
/tmp/previous-findings.json cover other quick-setup ideas (--ref, --audit, remote auto-detect, presets/list) but not piped token prompting.
What is this? | From workflow: Trigger Product Manager Impersonator
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
Feature Idea
Summary: Update
scripts/quick-setup.shso users can still pasteCOPILOT_GITHUB_TOKENwhen running the documentedcurl ... | bashsetup flow.Why a Customer Would Want This
The default onboarding path is a piped command, but token entry currently requires terminal stdin. First-time adopters can hit a hard failure unless they already know to pre-set
COPILOT_GITHUB_TOKENor use--skip-secret, which adds friction at exactly the moment setup should be easiest.Rough Implementation Sketch
scripts/quick-setup.shthat reads from/dev/ttywhen stdin is non-interactive but a terminal is available.--skip-secret, and dry-run).Why It Won't Be That Hard
This is a tightly scoped shell-script change in one code path (
tokenacquisition) with no workflow schema/compiler impact and no behavior changes to existing successful setup flows.Evidence
docs/index.mdlines 62-67 andREADME.mdlines 32-35.COPILOT_GITHUB_TOKEN:docs/index.mdlines 69-74.[ -t 0 ]), otherwise exits with an error:scripts/quick-setup.shlines 225-245.repo:elastic/ai-github-actions is:issue is:open "stdin is not a terminal" quick-setuprepo:elastic/ai-github-actions is:issue is:open quick-setup token promptrepo:elastic/ai-github-actions is:issue is:open quick-setup --skip-secret COPILOT_GITHUB_TOKEN/tmp/previous-findings.jsoncover other quick-setup ideas (--ref,--audit, remote auto-detect, presets/list) but not piped token prompting.What is this? | From workflow: Trigger Product Manager Impersonator
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.