Sync a GitHub repository
Connect GitHub and keep repositories synced into a vault, with automatic updates and delete propagation.
Connect your account
Open Connect → Connectors and choose Connect GitHub. This sends you to GitHub's own installation screen, where you pick exactly which repositories LiquidLM may read — a single repo, several, or all of them. You can change that selection on GitHub at any time.
LiquidLM never sees your GitHub password and stores no personal token. Access works through the GitHub App installation you grant; uninstalling the app on GitHub revokes it immediately.
- The app requests read-only permissions: repository contents and metadata. It cannot write to your repositories.
- Reinstalling after a revocation reactivates the existing connection — synced items are kept.
Add a repository
With the account connected, pick a repository, optionally a branch (the default branch is used when empty), and a target vault. The default suggestion creates a new vault named after the repository, which keeps scoping and removal simple; syncing several repositories into one vault also works.
The first sync walks the branch's full tree and indexes every eligible file. Repository files appear in the vault under an owner/repo folder, mirroring the repository's directory structure.
- Text-like files (code, docs, config) are synced by default. Connector files use the same per-file size limit as uploads on your plan.
- Vendored bulk — node_modules, lockfiles, minified bundles, build output — is never fetched, and neither are secret-shaped files such as .env files or private keys.
- Binary media (images, audio, video) is skipped by default; include patterns can opt specific paths in via the API.
How updates flow
Pushes to the synced branch reach LiquidLM through a webhook, so changes normally index within moments. A daily reconcile pass backstops any missed delivery, and Sync now forces a pass at any time.
Changed files re-index as overwrites of the same knowledge item, preserving file version history and attribution. Files deleted or renamed in the repository move to the vault's Trash, where they stay recoverable for the usual retention window.
- Sync writes are attributed to the connector, so audit feeds and last-modified fields never look like a human edit.
- Changing a source's branch or filters triggers a full re-inventory on the next sync.
Limits and health
Each plan includes a number of connected accounts and synced repositories. Very large repositories — beyond GitHub's tree-listing limit of about 100,000 entries — cannot be synced and fail with a clear error instead of syncing partially.
Every repository row shows its status, last sync time, and last error; History lists recent runs with added/updated/deleted counts. Synced files meter against the same storage and indexing quotas as uploads.
Have the right to sync it
Connecting a repository that belongs to an organization requires that you are authorized to grant that access, and you must have the right to copy and index the content — see the Terms of Use.