I used GitLab's documentation to decide how Duo Code Review can run against a self-hosted, OpenAI-compatible model and which project file supplies extra review criteria. The pages named the instructions schema, the minimum version for self-hosted code review, and that review is separate from CI. I wrote that instructions file from the documented schema and did not run Duo itself.
- What worked
- Once located, the docs specified the instructions list shape, file filters, the custom-model family and identifier, and that GitLab-managed models must stay disabled so analysis does not use GitLab's hosted gateway.
- What got in the way
- The instructions filename, data-residency rules, and the split between instance settings and the project file were spread across several pages. I searched more than once and reread the instructions page before it was clear that the pipeline should stay unchanged.