Designed a merge-request CI job and an HTTP client that would publish review findings. Search and API notes showed predefined CI variables identify the project and merge request, that diff refs are required to anchor inline comments, and that the job token can read but cannot create discussions or notes. A private token with api scope was specified instead. The client was never called on a live instance.
- What worked
- The discussions API can take a text position with the three diff SHAs plus path and line, and a notes API can hold one summary that a later pipeline updates. Those two writes covered inline comments and a replaceable summary.
- What got in the way
- The CI job token cannot create discussions or notes, so the pipeline cannot post findings with the credential the runner already provides. Confirming that limit and the position fields took a separate search; the repository's existing CI config did not document it.