test: Remove --no-prompt flag from Apify CLI push command in E2E tests

[Copilot]

Changes

Removed the --no-prompt flag from the apify-cli@beta push command in the E2E test suite (test/e2e/tools.mjs).

Why

The --no-prompt flag is no longer necessary because:

1. The Apify CLI is already authenticated in the GitHub workflow before E2E tests run (via npx -y apify-cli@beta login -t in .github/workflows/test-e2e.yml)
2. With proper authentication in place, the CLI won't prompt for user input during the push operation
3. This simplifies the command and aligns with the standard CLI usage pattern

Impact

This change only affects E2E tests running with STORAGE_IMPLEMENTATION=PLATFORM, where actors are pushed to the Apify platform for testing. The behavior remains the same since authentication is handled at the workflow level.

Modified file: test/e2e/tools.mjs

• Changed: execSync('npx -y apify-cli@beta push --no-prompt', { cwd: dirName });
• To: execSync('npx -y apify-cli@beta push', { cwd: dirName });

Original prompt

remo --no-prompt flag from the Apify CLI calls in E2E tests (its a workflow)

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.