Skip to main content
Orchestra Local works on repositories hosted on GitHub, GitLab (gitlab.com or self-managed) and Bitbucket Cloud. Your checkout is recognised from its origin remote, with no setup.

What works

  • Why a line changed and orchestra pr describe, using the merge request (GitLab) or pull request (Bitbucket) for your branch.
  • Pull requests, CI and shipping state for the repository: open and merged requests, pipeline runs with the tail of a failing job’s log, and recent tags. GitLab reads releases and deployments too. Bitbucket Cloud has no releases, and deployments are not read.
  • Code search and file reads come from your checkout, as on every host.
Everything is read from your laptop with your own sign-in. Nothing passes through Orchestra’s servers.

Sign in

Orchestra uses a sign-in you already have and never prompts. It looks in this order and takes the first it finds. With none, requests go out anonymously and only public repositories answer. For a private repository, a GitLab token needs the api scope, and a Bitbucket token needs repository and pull request scopes (add pipelines read for CI state). An Atlassian API token signs the Bitbucket API with your account email, while git uses your Bitbucket username, so set BITBUCKET_EMAIL when the token comes from git’s credential helper. Credentials are sent only to that host’s own API.

Not covered yet

Starting cloud sessions on GitLab or Bitbucket repositories is not available. Connect GitHub covers that today: see Connect GitHub.