Skip to main content

🌐 Supported SCM Providers

Early AI supports multiple source control platforms for test generation.
This page outlines which providers are supported and how to configure the --scm-provider flag for each one.

🛠️ How It Works​

All CLI-based agents accept the --scm-provider flag (or SCM_PROVIDER environment variable).
This tells the agent how to interpret commit metadata and which API to use for reading/writing data.

Example:

early generate-commit --scm-provider github
early generate-folder --scm-provider bitbucket

✅ Supported Providers​

ProviderCLI ValueStatus
GitHubgithub✅ Supported
Bitbucketbitbucket✅ Supported
GitLabgitlab🟡 Planned

⚠️ If you omit the --scm-provider flag, the default is github.

🔍 Feature Support Matrix​

FeatureGitHubBitbucketGitLab
✅ Commit Detection✅ Yes✅ Yes🟡 Soon
✅ PR Metadata✅ Yes✅ Yes🟡 Soon
✅ Repo Scanning (Folder CLI)✅ Yes✅ Yes🟡 Soon
✅ Auto-Commit✅ Yes✅ Yes🟡 Soon
❌ NPM Package AuthPATApp PWPAT

⚙️ Example CLI Flags​

# GitHub (default)
early generate-commit \
  --scm-provider github \
  --token $GITHUB_TOKEN \
  --ref-name main \
  --commit-hash abc123

# Bitbucket
early generate-folder \
  --scm-provider bitbucket \
  --token $BITBUCKET_APP_PASSWORD \
  --folder src/ \
  --ref-name develop

You can also pass the provider as an environment variable:

export SCM_PROVIDER=bitbucket
early generate-folder

🧪 CI Configuration Tips​

  • Bitbucket Pipelines: Use an App Password and store it securely.
  • Jenkins / CircleCI: Make sure SCM_PROVIDER is set explicitly.
  • GitHub Actions: You can omit --scm-provider (defaults to github).

📎 Related Topics​