Connect repositories and product sources
Connect the GitHub repositories, branches, and feature-flag sources Cactus uses for this product.
Choose repositories
The native repository connection is GitHub-based. Cactus doesn't provide a native GitLab repository connector.
In Settings › Sources, select Connect GitHub or Manage GitHub.
In GitHub, authorize Cactus or install its GitHub App.
Back in Settings › Sources, select Pick repositories. If the page says No repositories selected, select Open setup instead.
In the setup conversation, select the repositories that make up this product.
In the setup conversation, select Continue to save your selection.
Tracked branch
Cactus saves each selected repository with its default branch. Settings › Sources shows the branch Cactus reads.
Remove a repository
In Settings › Sources, select Remove beside the repository. Cactus stops reading it in future product refreshes. Already-published pages stay until the next refresh.
Connect feature flags
Connect PostHog or LaunchDarkly to give Cactus feature-flag context.
Connect PostHog
In Settings › Sources, select Connect PostHog.
Complete the PostHog authorization when prompted.
Connect LaunchDarkly
In Settings › Sources, select Connect LaunchDarkly.
Enter a LaunchDarkly access token with the Reader role in Reader token.
Select Find projects. Cactus lists the projects the token can access.
Choose a Project and Environment.
Select Save. Cactus checks that the token can access the chosen project and environment before saving.
Cactus initially selects the first project and its first environment. When you change Project, Cactus selects that project's first environment.
Use feature-flag context
Cactus reads flag state when it writes a page that checks a flag. Settings › Sources shows how many flag checks for each vendor Cactus finds in your code. If a flag changes, ask Cactus to republish the pages that check it.
Refresh on pushes
When GitHub reports a push to a selected repository's tracked branch, Cactus schedules a product refresh. For when that work runs and which pages it updates, see Keep product knowledge current.