Skip to main content
Vega integrates with GitHub to read your code, make code changes, and open pull requests. Connecting GitHub is optional for using Vega read-only mode. It is required for flag cleanup and for the agent mode flows that create pull requests. Connecting GitHub does not grant access to Vega itself. To use Vega, your role requires the Vega actions. To learn more about Vega, read Vega.

​
How GitHub access works

Vega’s GitHub access is scoped by both user and organization:
  • At the organization level, an admin installs the LaunchDarkly Vega GitHub App and selects which repositories Vega is allowed to access.
  • At the user level, each developer authenticates with their personal GitHub account.
The repositories Vega can access for a given user are the subset of repositories that user has access to, among the organization’s repositories that were granted access to Vega.
One GitHub organization per workspaceCurrently, LaunchDarkly supports connecting one GitHub organization per workspace.
Vega operates in private repositories onlyFor security reasons, Vega works only with private repositories. It will not read code from or open pull requests against public repositories, even if you grant the LaunchDarkly Vega GitHub App access to those repositories. This restriction prevents Vega from acting autonomously in a publicly visible codebase, where it could inadvertently expose secrets, configuration, or feature flag details in a pull request.

​
Setting up the GitHub integration

Vega may clone a connected repositoryIf you connect Vega to your GitHub account and you specify a repository when making a request, Vega may clone your repository code into an isolated environment to facilitate agent investigations.
To connect Vega to GitHub:
  1. Install the LaunchDarkly Vega GitHub App at the organization level.
  2. Authenticate with your personal GitHub account. This lets Vega act on your behalf by opening pull requests and reading from repositories you can access.
  3. Choose which repositories Vega can access. You can restrict Vega’s permissions to specific repositories. These access scopes apply across all modes and can be modified at any time from your GitHub organization’s settings.
All GitHub interactions are logged and scoped to your authenticated session. Vega will only operate within the repositories and permissions you’ve explicitly approved.

​
When GitHub is required

Vega featureGitHub required?
Read-only modeOptional (uses code context to improve analysis)
Agent modeOptional to select, required to create pull requests
Flag cleanupRequired (creates pull requests)
Search assistantNot used