Skip to content

Roadmap: self-hostable maintainer-automation stack + gittensory convergence #975

Description

@JSONbored

Overview

This roadmap tracks making the maintainer-automation stack (automated PR review + triage) self-hostable — so any repo maintainer can run it on their own infrastructure — and converging it into gittensory.

Today the automation runs as a hosted service on a serverless platform. The work below decouples the core from that platform, packages it as a one-command Docker stack, and makes the AI backend pluggable so a self-hoster can use free/open models, their own API keys (BYOK), a local model, or their own Claude Code / OpenAI Codex subscription for frontier-model reviews.

The hosted service stays live and unchanged throughout — this is additive and migration-safe.

Goals

  • Run the same automation core on the hosted platform and a self-hosted Node/Docker container.
  • One-command self-host (docker compose up) with sensible OSS-infra defaults.
  • Pluggable AI: free · BYOK API · local (Ollama / OpenAI-compatible) · subscription (Claude Code / Codex).
  • Clear per-project configuration and secure secret/credential handling.
  • Strangler-fig convergence into gittensory — per-repo, with parity verification and rollback.

Sub-issues

Principles

  • No regressions to the live hosted service; cut over per-repo only on an explicit signal.
  • Fail-safe: any backend/adapter failure degrades to manual review — never a wrong automated action.
  • Portability: the shared core carries no platform-specific dependencies.
  • Implementation-sensitive review heuristics, prompts, and policy specifics are intentionally kept out of public tracking and remain server-side defaults.

Metadata

Metadata

Assignees

Labels

maintainer-onlyOwner-only work — yields no Gittensor points.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions