The review system for GitLab. One decision before you release.
RCode reads the pipeline, the security scans, the tests, and the review discussion, then scores each merge request GO, REVIEW, or BLOCK. A person still approves the merge.
For GitLab merge requests · Human approval stays with you
Verdicts
GO, REVIEW, or BLOCK
Every open merge request gets one decision, a risk score, and the reasons behind it.
GO
The pipeline is green, the scans are clear, and the review evidence supports a release.
REVIEW
A person should look. The score explains what is unfinished or unclear.
BLOCK
Do not release. A failed check, a conflict, or a missing review stops the merge.
What it checks
A review built from GitLab evidence
RCode does not invent a result. The decision comes from the merge request that is open right now.
Pipeline evidence
A merge request with a failed or unfinished pipeline is never a GO. The decision uses the pipeline that is running now.
Security scans
Secret detection, dependency scanning, and SAST findings on the merge request are part of the score.
Tests and change size
RCode looks at whether tests changed and how large the diff is, then says why the risk moved.
Review discussion
Human comments and the gatekeeper verdict count. A stranger cannot forge a decision.
Agent trail
Triage, code review, and the release check are recorded, so you can see who prepared the decision.
A person still merges
RCode prepares the decision. It does not merge or deploy. Approval stays with your team.
FAQ
Questions before a release
GitLab merge requests. It reads the pipeline, security scans, tests, conflicts, and the review discussion, then returns GO, REVIEW, or BLOCK.
No. RCode prepares the decision and the reasons. A person on the project approves and merges.
GO means the evidence supports a release. REVIEW means a person should look before merging. BLOCK means do not release until the failed check is fixed.
From the GitLab project you connect: pipeline jobs, security reports, and review notes. RCode does not invent a result.
Review the merge request, then release.
Open RCode on your GitLab project and read the decision before you merge.
Open the review