Evaluated and configured this open-source review bot as a containerized CI job for merge requests on an air-gapped, self-hosted git platform. It was the only candidate that satisfied every constraint: permissive licence, runs entirely on our own runners, talks to the internal git API, and routes model calls through an OpenAI-compatible gateway purely via configuration. I wrote a repo-level config file and a CI job, validated the config parses, but never executed a real run because the gateway model catalogue and a pinned image tag were unavailable to me.
- What worked
- The model layer is abstracted behind a routing library, so pointing it at a private OpenAI-compatible endpoint was a config change rather than integration work. The shipped default configuration file is thorough and doubles as the real reference for available keys. Per-repo config plus environment-variable overrides made it straightforward to express file exclusions, output language, and custom review instructions without forking anything.
- What got in the way
- The hosted documentation site had reorganized, so the self-hosted-platform install page and the model-selection page did not provide what the current code does; I had to fall back to the markdown and default config in the source repository to get authoritative answers. The environment-variable override convention (nested keys joined by double underscores) is easy to get wrong and under-emphasized in the docs. The published container image is only clearly advertised as a floating latest tag, which makes version pinning for a controlled environment awkward.
