GitLab Integration
Connect a GitLab group once and every merge request in the repositories you pick gets reviewed. Add the IronBee GitLab component and each one is verified against your running app, with the verdict on the merge request itself.
Connect GitLab. Every merge request gets reviewed and verified.
- A merge request opensOr gets a push. IronBee picks it up on its own, with no one asking.
- Reviewed on its linesCode review reads the change with your team's rules and memories, and opens a thread on each finding with a suggestion.
- Verified in a real browserThe GitLab component drives the change against your real backend, on IronBee or on your own runner.
- Both on the merge requestThe review and the verification each post their findings, with a pipeline status where IronBee writes one. The evidence is in the Console.
Connect the group once. From then on every merge request in the repositories you pick is reviewed, the GitLab component verifies it in your pipeline, and the evidence lives in the Console.
A review on the lines of the change
IronBee posts a review note with an inline thread on each finding and a GitLab suggestion, keeps a summary note on the merge request, and sets the IronBee review pipeline status where it writes one.
invoice-pdf into mainChangessrc/main/java/app/billing/InvoiceController.java+21−0 } @GetMapping("/invoices/{id}/pdf") public ResponseEntity<byte[]> download(@PathVariable long id, Principal user) { Invoice invoice = invoices.findById(id).orElseThrow();Any signed-in customer can download any other customer's invoice: it is looked up by its id alone, never by its owner.
Happens when: a customer changes the number in /invoices/1042/pdf to another one.
Invoice invoice = invoices.findById(id).orElseThrow(); Invoice invoice = invoices.findByIdAndOwner(id, user.getName()).orElseThrow();Rule tenant-isolation a customer only ever reads their own records.
return ResponseEntity.ok(pdf.render(invoice)); }The whole run, on the merge request
With the GitLab component, the run lands in the same merge request: what the agent did, what it found, and where it came from, as a summary note and inline comments.
IronBee Verification
Verification failed1 critical · 1 medium
InvoiceController.java:29InvoiceController.java:29- Signed in as a customer and downloaded their own invoice
- Signed in as another customer and opened the first one's invoice link
- Opened an invoice id that does not exist
- Signed out and opened an invoice link: sent to sign in
View the full verification →Used 3 IronBee credits.
A service account, never your name
IronBee works in the group through an account of its own, on the repositories you pick. The token GitLab gave for your account is revoked as soon as the group is connected.
Its own service account
IronBee creates a service account in the group, a Maintainer that uses no seat. Reviews, replies and statuses are posted under it.
Read-only where your code runs
Code is checked out by an IronBee reader account with the Reporter role, and each job's token is revoked when the job ends.
Merges held only when you ask
IronBee's statuses join the merge request's pipeline. On a project with Pipelines must succeed, they hold a merge only once Block merges is turned on.
Reviewing and verifying merge requests, answered.
How the GitLab connection and the IronBee GitLab component review and verify every merge request.
Connect a top-level group on gitlab.com from the IronBee Console and pick its repositories. IronBee then reviews every merge request in them: a review note, an inline thread on each finding with a suggested fix, a summary note and the IronBee review pipeline status. Mention @ironbee-ai on a merge request to ask for a review.
IronBee across your workflow
IronBee for Vercel
Every preview deployment gets driven.
IronBee for Netlify
Every successful site deploy gets verified.
IronBee for GitHub
Every pull request reviewed, with a check.
IronBee for Bitbucket
Every pull request reviewed, with a build status.
IronBee for Cursor
Verify what your Cursor agents ship, right inside the editor.