🚀 Feature Request
Add a --no-gha option to create-playwright so callers can skip GitHub Actions workflow generation non-interactively.
This is especially useful for AI agents running setup CLIs. If an agent provides explicit scaffold flags but still hits an Add a GitHub Actions workflow? prompt, the setup flow becomes brittle. Agents sometimes answer prompts incorrectly or fail to continue, then fall back to generating project files from stale model knowledge instead of using the official generator.
There is already a related implementation attempt here:
Example
pnpm create playwright --no-gha
This would:
- skip the interactive
Add a GitHub Actions workflow? prompt
- continue scaffolding without creating the workflow
Motivation
Official CLIs work better for AI agents when all meaningful setup choices can be expressed as flags. Deterministic, non-interactive runs reduce prompt handling failures and make it more likely that agents keep using current Playwright defaults instead of scaffolding projects themselves.
Next.js recently moved create-next-app in the same direction so explicit CLI flags can avoid interactive prompts and remain agent-friendly:
Adding --no-gha would make create-playwright easier to automate and more consistent with the wider JS tooling ecosystem.
Related:
🚀 Feature Request
Add a
--no-ghaoption tocreate-playwrightso callers can skip GitHub Actions workflow generation non-interactively.This is especially useful for AI agents running setup CLIs. If an agent provides explicit scaffold flags but still hits an
Add a GitHub Actions workflow?prompt, the setup flow becomes brittle. Agents sometimes answer prompts incorrectly or fail to continue, then fall back to generating project files from stale model knowledge instead of using the official generator.There is already a related implementation attempt here:
Example
This would:
Add a GitHub Actions workflow?promptMotivation
Official CLIs work better for AI agents when all meaningful setup choices can be expressed as flags. Deterministic, non-interactive runs reduce prompt handling failures and make it more likely that agents keep using current Playwright defaults instead of scaffolding projects themselves.
Next.js recently moved
create-next-appin the same direction so explicit CLI flags can avoid interactive prompts and remain agent-friendly:Adding
--no-ghawould makecreate-playwrighteasier to automate and more consistent with the wider JS tooling ecosystem.Related:
create-playwrightoption--no-ghato skip GitHub Actions workflow question #33243