​
Overview

Blink has access to understand and review all the repositories you give it access to through your GitHub integration. Unlike many AI coding assistants that limit you to one repository per chat, Blink can work across multiple repositories within the same conversation.

​
How Multi-Repo Works

Once you’ve connected your GitHub account, Blink can:
  • Access multiple repos: Review code, issues, pull requests, and documentation across all your connected repositories simultaneously, giving you comprehensive visibility into your entire development ecosystem.
  • Switch contexts seamlessly: Move between different repositories within the same chat conversation without losing context or needing to start fresh sessions for each codebase.
  • Maintain conversation history: Keep all context and discussion history from previous repository interactions within the same chat, allowing for complex multi-repo workflows and decision-making processes.

​
Key Benefits

​
Consistent Patterns Across Repositories

Implement the same coding patterns, configurations, or architectural decisions across multiple projects: 
Apply the same ESLint configuration from my frontend-app repo to my backend-services repo

​
Cross-Repository Dependencies

Research and understand how your repositories interact with each other: 
Show me how the user authentication flow works between my auth-service and web-client repositories

​
Comparative Analysis

Compare implementations, patterns, or approaches across different repositories: 
Compare the error handling patterns in my user-service, payment-service, and notification-service repositories

​
Using Multiple Repositories

​
Explicit Repository References

Be specific about which repository you want Blink to work in: 
In the coder/coder repository, find all instances of the login function

​
Shortcuts for Repository Context

Create shortcuts to quickly reference frequently used repositories: 
@frontend-repo - Focus on the company/frontend repository
@backend-repo - Focus on the company/backend repository
If you don’t specify a repository, Blink will ask:
  • “Which repository should I focus on?”
  • “Are you referring to the frontend or backend repository?”
  • “I see multiple repositories - which one contains the code you’re asking about?”

​
Best Practices

  • Be explicit: Always specify which repository you’re working with to avoid confusion and ensure Blink focuses on the correct codebase for your specific task or question.
  • Use shortcuts: Create repository-specific shortcuts for common workflows to streamline your multi-repo development process and reduce repetitive context-setting.
  • Leverage cross-repo insights: Take full advantage of Blink’s unique ability to see patterns, dependencies, and relationships across your entire codebase ecosystem rather than treating repositories in isolation.
  • Organize by context: Group related repository discussions within the same chat session to maintain context and enable more sophisticated cross-repository analysis and decision-making.