Skip to content

VCS providers

Cascade auto-detects which VCS your repo is hosted on from the git origin URL and opens the PR on the right service.

ProviderSelf-hostedDefault base URL
GitHubYes (GitHub Enterprise via --base-url)https://api.github.com
GitLabYes (cloud + self-hosted)https://gitlab.com
Bitbucket CloudCloud only in v0.1https://api.bitbucket.org/2.0
Azure DevOps ReposYeshttps://dev.azure.com
Terminal window
cascade configure vcs github --token ghp_xxx

Token needs repo scope. Create one at https://github.com/settings/tokens.

For GitHub Enterprise:

Terminal window
cascade configure vcs github --token ghp_xxx --base-url https://github.acme.com/api/v3
Terminal window
# gitlab.com
cascade configure vcs gitlab --token glpat-xxx
# Self-hosted
cascade configure vcs gitlab --token glpat-xxx --base-url https://gitlab.acme.io

Token needs api scope. Create one at your GitLab profile settings.

Terminal window
# Using an App Password (recommended)
cascade configure vcs bitbucket --token "your_username:your_app_password"
# Using a workspace token
cascade configure vcs bitbucket --token your_workspace_token

App Passwords need write access to “Pull requests”.

Terminal window
cascade configure vcs azure_devops --token your_pat --organization myorg

PAT needs Code (Read & Write) and Pull Request Threads (Read & Write) scopes.

When cascade build runs, it reads the repo’s git remote get-url origin and parses the URL. The hostname determines the provider:

URL patternDetected as
github.com/owner/repoGitHub
gitlab.com/group/project or any URL containing gitlabGitLab
bitbucket.org/team/repoBitbucket
dev.azure.com/org/project/_git/repoAzure DevOps

Both HTTPS and SSH origin URLs are recognized.

If you have a non-standard URL or your repo is mirrored, you can override the provider in ~/.config/cascade/config.yaml:

defaults:
vcs_provider: gitlab

Cascade writes a structured PR description that includes:

  • The story title and description
  • All acceptance criteria
  • A list of every file changed with the reason
  • Test command, result, and summary
  • Attribution back to Cascade with the story ID and source

The format renders well on every supported VCS.

  • Bitbucket Server (Data Center) support
  • Gitea / Codeberg support
  • Merge request comment loop (Cascade reads review comments and iterates)