Problem
The CLI has two entry points for a project. apify create starts from nothing, and apify pull starts from an Actor that already exists. There is no path for the case most existing developers arrive with: a repository that already exists, possibly with several packages, that should become an Actor. init only writes actor.json. Nothing binds the directory to an Actor or sets the repo as its Git source, so people wire it in Console by hand (#1425, #1428).
What we want
apify import: run inside an existing repo, bind it to a new or existing Actor, and optionally set the Actor's Git source to the repo, branch, and subdirectory. The reverse of create --source, reusing its provider authorization.
Links
Problem
The CLI has two entry points for a project.
apify createstarts from nothing, andapify pullstarts from an Actor that already exists. There is no path for the case most existing developers arrive with: a repository that already exists, possibly with several packages, that should become an Actor.initonly writesactor.json. Nothing binds the directory to an Actor or sets the repo as its Git source, so people wire it in Console by hand (#1425, #1428).What we want
apify import: run inside an existing repo, bind it to a new or existing Actor, and optionally set the Actor's Git source to the repo, branch, and subdirectory. The reverse ofcreate --source, reusing its provider authorization.Links
apify pushwith monorepo projects #595 (existing repo and monorepo), No CLI surface for git integrations — --source github dead-ends on an unconnected workspace #1428 (git integrations), feat: turn on automatic builds for a Git-sourced Actor #1377 (auto-build)vercel link