Pipeline evidence
A merge request with a failed or unfinished pipeline is never a GO. The decision uses the pipeline that is running now.
FEATURES
Every check behind a release decision
Pipeline, security scans, tests, and the review discussion. One decision for the GitLab merge request.
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.
Open a merge request
Read GO, REVIEW, or BLOCK for the merge requests in your GitLab project.
Open the review