By connecting a Git repository to Super, you can search and ask questions across the documentation and source files in that repo. Super clones your repo over Git and indexes its contents directly.
This article covers connecting a Git repository, what gets indexed, the Index code option, and permissions.
Connecting Git & Super
Required Permissions for Setup
To connect Super and Git, you must have the necessary permissions* in both platforms.
In Super: Permission to add or remove data sources depends on your team's settings. By default, only workspace admins or owners can set up a connection. However, a Super admin can enable a setting to allow all members to add and remove data sources.
In Git: You need a repository URL Super can reach over HTTPS or SSH, plus an SSH private key if you're using the SSH transport. For private repos, the key must have read access to the repository.
*If you don't have these permissions, ask your Git admin to provide the repository URL and SSH key.
Initial Git Connection
In Super, click Data Sources in the sidebar.
Click + New source , then choose or search for Git and click Add a repository .
Enter your Repository URL — Super accepts SSH ( git@github.com:org/repo.git ) or HTTPS ( https://example.com/foo/bar.git ).
(Optional) Toggle Index code on if you want Super to index all source files in the repo, not just markdown documentation. See The Index code option below for what this changes.
(Optional) Paste your Private SSH key if you're using the SSH transport. Leave blank for HTTPS.
Click Submit .
Large repositories may have longer initial sync times
How Super uses your Git data
Super clones your Git repository over the Git protocol and indexes the files in it. By default, only markdown (.md) files are indexed — typically your documentation, READMEs, design docs, and runbooks.
Super re-syncs each repository every 6 hours. Files that haven't changed are skipped, so re-syncs are fast.
The Index code option
When Index code is enabled on a connection, Super also indexes all other text files in the repository (source code, config files, scripts), not just markdown. Each indexed file can be up to 512 KB; larger files and binary files are skipped.
Indexing code is only available through the Git source. The GitHub and GitLab connectors index issues and pull/merge requests only — to index a repository's source files, connect it as a Git source, even if it's hosted on GitHub or GitLab.
You can toggle this at connection time or later — open the 3-dot menu on the Git connection in the Data Sources panel and click Edit settings.
Access Control & Privacy
Git is a Shared source: once a repository is connected, its content is available to your Super workspace as a whole rather than being matched to each user's permissions in your Git host.
By default a newly connected repository is restricted to workspace admins. To open it to more people, go to the connection in the Data Sources panel and adjust access. See Controlling access to shared sources for details.
Frequently asked questions
Does Super write back to my repository?
No. Super clones your repo read-only and never pushes, commits, comments, or modifies anything on the remote.
What does "Index code" actually index?
All text files in the repository, including source code, config files, and scripts. Files larger than 512 KB are skipped, and binary files are detected and excluded automatically. With Index code disabled (the default), only .md markdown files are indexed.
Can I update the SSH key or change Index code after connecting?
Yes. Open the 3-dot menu on the Git connection in the Data Sources panel and click Edit settings.
How often does Super re-sync the repository?
Every 6 hours. Files with unchanged content are skipped, so re-syncs are fast even for large repos.