GitHub repositories, synced into your vault
Connect a GitHub App, pick the repos LiquidLM may read, and keep eligible files indexed as your team pushes — with deletes landing in Trash.
Why this exists
Most teams already keep the durable decisions in a repository: policies, ADRs, runbooks, product notes. Pasting those into a chat every morning does not scale, and a one-off export goes stale the next push.
LiquidLM’s GitHub connector keeps selected repositories flowing into a vault so chat, MCP, API, and CLI all search the same inspectable copy — without asking you to manage a personal access token.
How connection works
Open Connect → Connectors and choose Connect GitHub. GitHub’s own installation screen asks which repositories LiquidLM may read. You can narrow that selection later on GitHub at any time.
- Access is a GitHub App installation — LiquidLM never sees your GitHub password and does not store a personal token.
- Permissions are read-only: repository contents and metadata. The app cannot write to your repositories.
- Uninstalling the app on GitHub revokes access immediately. Reinstalling reactivates the existing LiquidLM connection without wiping already-synced items.
What gets indexed
After the account is connected, pick a repository, an optional branch (default branch when empty), and a target vault. The first sync walks the branch tree and indexes every eligible file under an owner/repo folder that mirrors the repository layout.
- Text-like files — code, docs, config — sync by default, under the same per-file size limit as uploads on your plan.
- Vendored bulk (node_modules, lockfiles, minified bundles, build output) and secret-shaped files (.env, private keys) are never fetched.
- Binary media is skipped by default; include patterns can opt specific paths in via the API when you need them.
How updates stay current
Pushes to the synced branch reach LiquidLM through a webhook, so changes normally index within moments. A daily reconcile pass backstops missed deliveries, and Sync now forces a pass whenever you need one.
Changed files re-index as overwrites of the same knowledge item, preserving file version history. Files deleted or renamed in the repository move to the vault’s Trash and stay recoverable for the usual retention window.
- Sync writes are attributed to the connector in audit feeds, so they never look like a human edit.
- Changing a source’s branch or filters triggers a full re-inventory on the next sync.
Limits to know
Each plan includes a number of connected accounts and synced repositories. Very large trees — beyond GitHub’s listing limit of about 100,000 entries — fail with a clear error instead of syncing partially. Synced files meter against the same storage and indexing quotas as uploads.