Gitea Pull Request Review

If your organization uses Gitea for source control, the assistant can look up pull requests, read their diffs and discussion, and — with your approval — post review comments back to Gitea, all from chat.

This feature may not be available in all setups. It is part of an add-on plugin that not every edition of Codumentor ships, and your administrator must enable it and configure a Gitea server before it appears. If you don't see it working, it may not be enabled by your administrator.

Connecting your Gitea account

Each person uses their own Gitea access token, so the assistant always acts as you — there is no shared account.

1. In Gitea, go to Settings → Applications → Generate New Token. Grant repository read scope to look things up; add issue/PR write scope as well if you also want to post comments.
2. In Codumentor, go to Settings → Extensions → User Secrets → Add, name the secret gitea_api_token (your administrator may have configured a different name), and paste the token.

If you ask about a pull request before the token is set, the assistant tells you it's missing instead of trying and failing silently.

Asking about a pull request

Once connected, just ask in a normal message:

"List the open pull requests on our backend repo."

"What does PR #42 change? Summarize the diff."

"Who commented on PR #17, and what did they say?"

These reads never ask for approval — the assistant can list pull requests, fetch a PR's details, diff, changed files, commits and existing comments freely, and will cross-reference them against the ingested codebase when useful. For a large pull request, it prefers pulling individual changed files over the full diff.

Posting comments and reviews

Ask the assistant to comment on or review a pull request, and it drafts findings grounded in the actual diff:

"Review PR #42 and leave comments on anything risky."

"Post a summary comment on PR #17 saying it looks good to merge."

Posting a comment, a line-level comment, or an overall review verdict (comment / approve / request changes) each go through the normal approval dialog before anything lands on Gitea — nothing is posted without you seeing it first. If the assistant re-reviews the same pull request later (for example after a new push), it skips comments it already posted rather than repeating itself.

Automatic review on a webhook

Separately from chat, an administrator can wire Gitea webhooks so that opening a pull request, pushing new commits to one, or asking for a review (a /review comment, or Gitea's own "request review" action) automatically starts a review conversation — no one has to open Codumentor and ask.

This automatic path is off by default and must be explicitly configured and turned on by an administrator; most setups will only offer the chat-initiated review described above.

Where it is enabled, an automatic review can still only post comments — it can summarize findings and leave line comments, but it never submits an approve or request-changes verdict on its own. Approving or requesting changes on a pull request always requires someone reviewing it interactively in chat and confirming through the approval dialog.