Git-sourced Actor flow (GitHub/GitLab/Bitbucket, ...) · Issue #1237 · apify/apify-cli · GitHub
Skip to content

Git-sourced Actor flow (GitHub/GitLab/Bitbucket, ...) #1237

Closed

Description

@DaveHanns

Add the Git-sourced creation path so apify create hands the local scaffold to a provider. The full flow is in the Epic.

  • Add --source apify|github|gitlab|bitbucket (default apify) and --git-repo owner/name.
  • Implement the connect flow: scaffold locally, have the Apify platform create the repo and Actor, then push.
  • Keep it provider-agnostic (the browser does the auth) and non-interactive when already authorized.
  • ... see parent epic for additional context.

Out of scope: registering an existing repo (the mirroring command of Import from Git button).

Activity

  1. changed the title [-]`apify create --source <provider>`: Git connect flow (GitHub/GitLab/Bitbucket)[/-] [+]Git-sourced Actor flow (GitHub/GitLab/Bitbucket, ...)[/+] on Jun 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request.t-buildersIssues owned by the Builders team.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions