GitHub

GitHub holds the source of truth for code, infrastructure, and engineering process at most modern companies. The integration lets myai ingest private repositories so codebases become searchable, citable, and queryable from chats — for the moments when "where do we handle X" or "what does the auth flow actually do" needs a fast answer pulled from real code instead of someone's outdated memory.

What you can do

• Private repository ingestion — connect a token, point at the repo, myai pulls a snapshot for search and reference.
• Whole-repo full-text search — find every reference to a function, config key, error message, or comment across the codebase.
• File-level summaries — ask "what does this file do" and get a structured summary built from the actual code, not training-data guesses.
• Directory-tree navigation — for the "I know it's in the auth module but where exactly" questions.
• On-demand re-ingestion — when the repo moves, rerun the ingestion to refresh myai's snapshot.

How to connect

GitHub Personal Access Token (PAT). The token is stored in Google Secret Manager and read only when myai clones a repo on your behalf.

Generate a PAT at Settings → Developer settings → Personal access tokens on github.com:

• Classic PATs — select the repo scope (full control of private repositories) for private repo access.
• Fine-grained PATs (recommended) — select the specific repositories you want myai to read, and grant Contents: Read permission. Tightest scope.

Public repositories don't require a credential. Only connect this integration if you plan to ingest a private repo.

Connect GitHub in myai

Common use cases

• Onboarding accelerator — new engineer asks "where do we handle X" in chat, gets the answer pulled from the actual codebase with file paths.
• Documentation gap surfacing — function compares the README + ARCHITECTURE.md against the actual code, flags components that have drifted.
• Cross-tool engineering queries — combine GitHub code references with Linear issue context for the full picture of what changed and why.

Reference

• Connection model: GitHub Personal Access Token (PAT) — stored in Google Secret Manager
• Recommended: fine-grained PAT scoped to specific repos with Contents: Read
• Public repos don't require auth — use the integration only for private repo access