From 9aaa40eb91caa3eeeb64aa7dc492e8f6b5014b44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Hanu=C5=A1?= Date: Sun, 5 Jul 2026 13:58:39 +0200 Subject: [PATCH] docs(apify-actor-development): clarify `apify push` needs `apify login`, not just APIFY_TOKEN --- skills/apify-actor-development/SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/skills/apify-actor-development/SKILL.md b/skills/apify-actor-development/SKILL.md index ce02412..ffbc06f 100644 --- a/skills/apify-actor-development/SKILL.md +++ b/skills/apify-actor-development/SKILL.md @@ -48,6 +48,10 @@ apify login If browser login isn't available (headless environment or CI), the CLI automatically reads `APIFY_TOKEN` from the environment. Ensure the env var is exported and run any apify command - no explicit login needed. If the user doesn't have a token, generate one at https://console.apify.com/settings/integrations. +> **Headless / CI note:** `apify info` and `apify api` read `APIFY_TOKEN` from the environment, but `apify push` reads its token from `~/.apify/auth.json` populated by `apify login`. In a non-interactive environment where you cannot complete the OAuth flow, run `apify login --token "$APIFY_TOKEN"` once at session start; otherwise `apify push` fails with a 401 despite `apify info` succeeding. +> +> `apify push` is already non-interactive once a token is stored — there is no `--yes` / `--no-prompt` flag. Use `apify push --force` to skip the confirmation when overwriting a build of an existing version. + > **Security note:** Avoid passing tokens as command-line arguments (e.g. `apify login -t `). > Arguments are visible in process listings and may be recorded in shell history. > Prefer environment variables or interactive login instead.