Patterns Overview
Simili Bot is designed to adapt to your organization’s workflow. Whether you’re managing a single project or a complex microservices architecture, there’s a pattern that fits.The three patterns
Choose a pattern based on your repository structure and how much autonomy your individual teams require.Pattern A: Single repository
The simplest setup, where the bot lives and runs entirely within one repository.- Best For: Small teams, standalone projects.
- Primary Benefit: Zero external dependencies and fast setup.
- Permissions: Default
GITHUB_TOKEN.
Pattern B: Centralized multi-repository
One “Control” repository manages issues across multiple “Target” repositories.- Best For: Organization-wide control, compliance, and unified routing.
- Primary Benefit: One place to manage all configuration and automation.
- Permissions: Elevated (GitHub App or PAT).
Pattern C: Distributed multi-repository
Every repository has its own bot and config, but they all share a centralized knowledge base.- Best For: Microservices, high team autonomy, cross-team discovery.
- Primary Benefit: Teams control their own bot while benefiting from organization-wide search.
- Permissions: Default
GITHUB_TOKENper repo.
Comparison matrix
| Feature | Pattern A | Pattern B | Pattern C |
|---|---|---|---|
| Setup Speed | < 5 mins | 15+ mins | 15+ mins |
| Team Autonomy | High | Low | High |
| Central Control | Local | Unified | Shared Defaults |
| Cross-Repo Search | No | Yes | Yes |
| Permissions | Basic | Elevated | Basic |