1. Install
Install the app for your organization or selected repositories using the GitHub App installation flow.
Auto-suggest the best assignee for every new issue.
Triavo analyzes repository activity and semantic commit context to recommend the most relevant contributor for newly opened issues.
Teams can review the recommendation immediately and apply it with /triavo assign.
How to Use Triavo
Triavo fits into a maintainer workflow with almost no extra process: install it once, open issues as usual, and use the recommendation when it looks right.
2. Let Triavo learn the repo
After installation, Triavo ingests recent commits, issues, pull requests, and contributor activity to build repository context.
3. Open a new issue
Create a new issue in an installed repository. Triavo automatically starts analysis as soon as the issue is opened.
4. Review the suggestion
Triavo comments with the strongest contributor match using semantic similarity, recent activity, contribution history, and workload-aware scoring.
5. Apply assignment
Comment /triavo assign to let Triavo assign the suggested contributor if they are assignable.
6. Keep signals fresh
Push events continuously add new commit embeddings, so future issue suggestions stay aligned with the latest work in the repository.
Best results come after installation and a bit of repository history, because Triavo relies on recent project context to rank contributors well.
How Triavo Works
Triavo turns webhook events into automated issue triage decisions.
- GitHub sends signed events to
/webhook. - Triavo validates signature and deduplicates delivery IDs.
- Issue open events trigger contributor ranking and semantic matching.
- Push events store commit embeddings for future issue similarity lookups.
- Triavo posts suggestion comments and supports command-driven assignment.
Signal blend: baseline contribution + semantic similarity + expertise boost - workload penalty.
Architecture Snapshot
API Layer
FastAPI service handles webhooks, scoring orchestration, and public status endpoints.
Primary Data
PostgreSQL stores webhook dedupe records and recommendation history.
Semantic Search
Qdrant stores commit embeddings and supports similarity queries for issue text.
GitHub Integration
GitHub API is used for contributors, commits, PRs, comments, and assignment actions.
Security and Data Controls
Triavo enforces webhook authenticity checks and limits processing to required repository activity for service functionality.
- HMAC signature verification via
X-Hub-Signature-256 - Unique webhook delivery tracking
- Credential-based access to GitHub, PostgreSQL, and Qdrant
- Infrastructure-hosted encryption in transit and controlled service access
FAQ
Why no suggestion posted?
Confirm app installation permissions, webhook secret correctness, and health readiness for dependencies.
Why assignment did not happen?
Use exact command /triavo assign and ensure the suggested user is assignable in the repository.
Where is full setup guidance?
Use the complete implementation guide at the documentation page.
Where are legal terms?
Privacy data handling details are published in the Privacy Policy page.