Connecting Vega to GitHub
Overview
Vega integrates with GitHub to read your code, make code changes, and open pull requests. Connecting GitHub is optional for using Vega investigate mode, but is required for fix mode and flag cleanup, both of which create pull requests.
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 workspace
Currently, LaunchDarkly supports connecting one GitHub organization per workspace.
Setting up the GitHub integration
Vega may clone a connected repository
If 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:
- Install the LaunchDarkly Vega GitHub App at the organization level.
- Authenticate with your personal GitHub account. This lets Vega act on your behalf by opening pull requests and reading from repositories you can access.
- 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.
