Getting Code Changes from GitLab MRs for Review

[Shailesh Chillarge]

We currently utilize GitLab and are aiming to build a similar internal utility tailored to our project requirements. Due to confidentiality constraints, we cannot expose our source code externally, which prevents us from using existing third-party solutions.

I have a query regarding this.

During the creation of a Pull Request (PR) or Merge Request (MR), how can we programmatically extract the associated code diffs and persist them to a file? The goal is to use this diff as input to an external API—specifically, a Large Language Model (LLM) for automated code review.

The intended workflow is to analyze the code changes using the LLM and then post the generated feedback directly on the PR/MR discussion thread. This would ensure that every code change undergoes an initial automated review before being evaluated by a human reviewer.

[David Trowbridge]

This mailing list is about the Review Board code review tool. It doesn't sound like you're using Review Board--you'll want to find a GitLab-specific forum to ask this question.

--

---
You received this message because you are subscribed to the Google Groups "Review Board Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-d...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/reviewboard-dev/8f52cf87-07b0-44b0-88f7-44a239aa7731n%40googlegroups.com.