[Feature]: `create-playwright` option `--no-gha` to skip GitHub Actions workflow question

[karlhorky]

🚀 Feature Request

Add --no-gha option to create-playwright to be able to skip the question of creating the GitHub Actions workflow, instead of requiring interactive input from the user

Already opened a PR for this, but it was closed because there's no companion issue yet:

• Add --no-gha option to skip GitHub Actions workflow create-playwright#130

Example

$ pnpm create playwright
Getting started with writing end-to-end tests with Playwright:
Initializing project in '.'
✔ Do you want to use TypeScript or JavaScript? · TypeScript
✔ Where to put your end-to-end tests? · tests
✔ Add a GitHub Actions workflow? (y/N) · false
✖ Install Playwright browsers (can be done manually via 'pnpm exec playwright install')? (Y/n) · true

$ pnpm create playwright --no-gha
Getting started with writing end-to-end tests with Playwright:
Initializing project in '.'
✔ Do you want to use TypeScript or JavaScript? · TypeScript
✔ Where to put your end-to-end tests? · tests
✖ Install Playwright browsers (can be done manually via 'pnpm exec playwright install')? (Y/n) · true

Motivation

Be able to run the script in a more automated, zero-config way, instead of having to input details interactively as a user.

[tphillips-ict]

I am not really sure how removing one question from a list of 4 makes the initialisation more script-friendly.
Maybe the responses to the questions should be able to be given on the command-line when running create playwright
Does --quiet achieve the same effect?

[karlhorky]

I am not really sure how removing one question from a list of 4 makes the initialisation more script-friendly.

Almost all of the other questions are already able to be passed via flags.

Unfortunately, the Playwright team declined one of the others I proposed:

• [Feature]: create-playwright --test-dir option #29891
• feat: create-playwright --test-dir option create-playwright#117

If I remember correctly, with --no-gha and --test-dir, it would enable create-playwright to be run non-interactively (in a configurable way, which --quiet is not - see below).

Maybe the responses to the questions should be able to be given on the command-line when running create playwright

Yes, agreed. This is a common pattern with scaffolding CLIs like create-next-app - all interactive questions should be specifiable via command line flags too.

Does --quiet achieve the same effect?

No, the --quiet flag is an unconfigurable list of defaults. (exception being the TEST_OPTIONS environment variable, which is discouraged (undocumented and internal))

[karlhorky]

Superseded by #39987