Connecting repositories
Guardix analyzes code from a Git snapshot (branch or commit). How you connect depends on whether the repo is private or public.
Private repositories
Section titled “Private repositories”- Install or authorize the GitHub App when the product prompts you.
- Select the organization and repositories you want Guardix to access.
- You can adjust access later in GitHub’s GitHub App settings for your org or user.
Private flows ensure Guardix only clones what you authorize.
Public repositories
Section titled “Public repositories”For open-source projects, you can often connect by URL without granting broad org access — useful for quick runs on public code.
Exact options may vary by environment; follow the in-app flow and any error messages (for example, duplicate connections).
Teams and ownership
Section titled “Teams and ownership”Repositories can be associated with a team workspace. Team admins and members should align on:
- Which team owns production audits
- Invite links for joining the team (Working with teams)
Troubleshooting
Section titled “Troubleshooting”- Missing repos — confirm the GitHub App is installed on the right org and that you granted repo access.
- Connection errors — read surfaced API errors in the UI; duplicate or invalid connections should be explained there rather than failing silently.
Next: Your first audit for a full walkthrough.