Linking Repositories

Once your GitHub account is connected, you can link a repository to any project. Each project can have one linked repository.

Linking a repository

1. Navigate to your project
2. Click the Context tab
3. Select the Codebase Context sub-tab
4. Click Link GitHub Repository
5. A modal appears listing all repositories available from your GitHub installations
6. Click Link to Project next to the repository you want

After linking, SprintVibe immediately starts syncing your codebase. You'll see a spinner with "Syncing codebase..." while the sync is in progress.

What happens during sync

When you link a repository, SprintVibe:

1. Fetches the file tree — Scans your repository's directory structure (up to 500 files)
2. Reads key files — Downloads important configuration and documentation files:
   • README.md, CLAUDE.md
   • package.json, Gemfile, requirements.txt, pyproject.toml, go.mod, Cargo.toml
   • tsconfig.json, next.config.*, vite.config.*, webpack.config.*
   • .env.example, docker-compose.yml, Dockerfile
   • db/schema.rb, prisma/schema.prisma, config/routes.rb
3. Generates an AI Codebase Profile — Uses AI to summarize your codebase into a structured profile (~2000 words)

The sync typically takes 1-2 minutes depending on repository size.

Primary and reference repos

Each project supports up to two linked repositories:

• Primary — the repo SprintVibe is actively planning for. Webhooks (PR merges, branch pushes) update story status here. Branch-name suggestions, GitHub Issue triage, and PR linking all target this repo.
• Reference — an optional second repo Vibe reads for patterns and inspiration only. No webhooks fire on this repo — pushing or merging here won't move stories. Use it when you're modeling work after a template, library, or prior project.

Both contexts are injected into AI prompts (sprint generation, Vibe chat, task generation) with clear labels so Vibe knows which repo to plan for and which is read-only context.

Add a reference repo from the wizard's "Connect your code" step or from the Codebase Context tab. You can swap which repo is primary at any time using the Swap button.

Unlinking a repository

1. Go to the project's Context → Codebase Context tab
2. Click the ✕ button next to the repository name
3. Confirm the unlink action

Unlinking removes the GitHub connection and all code context for that role. The repository itself is not affected.