Skip to content

Version control (GitHub, GitLab, Bitbucket)

Connecting a version-control provider is what makes AI remediation work. Once a repository is linked, BestDefense can generate a code fix for a finding, open a pull request in that repository, and track the PR’s status to drive your Remediation Queue. Without a connected repository, AI remediation has nowhere to put the fix.

  1. Go to Integrations and find the provider card (GitHub, GitLab, or Bitbucket).
  2. Choose Connect.
  3. Authorize BestDefense at the provider when prompted.
  4. You’re returned to BestDefense, and the card shows Connected.

The connection belongs to the organization you’re in. To connect a provider for a different organization, switch organizations first and connect again there.

Connecting the provider grants access; it doesn’t pick which repositories BestDefense should touch. After connecting, link the specific repositories you want BestDefense to work with. Only linked repositories are eligible for remediation pull requests.

So that scanning a target opens fixes against the right code, map a domain/target to a repository. When BestDefense remediates a finding from a scan of that target, it opens the pull request in the mapped repository.

You can also set the branch a repository’s fixes target, so pull requests open against the branch you expect (for example, your default development branch).

Availability varies by provider — always check the cards in the app for current status.

  • GitHub — fully supported: connect, link repositories, and receive remediation pull requests.
  • Bitbucket — connection is available.
  • GitLab — shown as coming soon; it’s on the roadmap and not yet generally available.

To disconnect, open the provider card and choose disconnect. This removes the linked repositories from BestDefense. It does not change anything on the provider side — no repositories, branches, or pull requests are altered there.