GitHub Integration
Install the GitHub App once and every pull request in the repositories you pick gets reviewed. Add the IronBee GitHub Action and each one is verified against your running app, with the verdict on the pull request itself.
Connect GitHub. Every pull request gets reviewed and verified.
- A pull 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 comments on each finding with the fix.
- Verified in a real browserThe GitHub Action drives the change against your real backend, on IronBee or on your own runner.
- Two checks on the pull requestIronBee review and IronBee Verification, each with its findings. The evidence is in the Console.
Install the app once. From then on every pull request in the repositories you pick is reviewed, the GitHub Action verifies it in your workflow, and the evidence lives in the Console.
A review on the lines of the change
IronBee reads the change with your team's rules and memories, comments on each finding with the fix, adds a summary to the pull request description and sets the IronBee review check.
coupons into mainFiles changedlib/coupons.ts+12−3export function applyCoupon(total: number, coupon: Coupon) { const rate = coupon.percent; return total; return total * (1 - rate / 10);A percent coupon is divided by 10, not 100, so TARE10 takes the whole order off.
Happens when: a customer applies any percent coupon. TARE10 turns a $42 order into $0.00.
return total * (1 - rate / 10); return total * (1 - rate / 100);Rule money-paths an amount shown to the customer is the amount charged.
}The whole run, on the pull request
With the GitHub Action, the run lands in the same thread: what the agent did, what it found, and where it came from, as the IronBee Verification check and a comment.
IronBee Verification
Verification failed2 high
lib/coupons.ts:14lib/cart.ts:41- Signed in and added a $42 item to the cart
- Applied TARE10 and compared the cart with the real Stripe session
- Checked out and compared the total shown with the amount charged
- Reached the order confirmation
View the full verification →Used 4 IronBee credits.
Read-only where your code runs
The app asks for what verification and code review need to do their job and nothing beyond it.
Read-only where your code runs
The verification agent checks out your code and does not write to your repository. Each code review gets a read-only token for that one repository, which expires in an hour.
Scoped to what you install it on
Choose the repositories the app can see when you install it, and change that at any time from GitHub.
Writes go to the pull request
Checks, reviews and replies are posted there. For code review the app also asks for Contents write, which GitHub requires to resolve a review thread, and Issues read, for linked issues and @ironbee-ai commands. It does not push commits.
Reviewing and verifying pull requests, answered.
How the IronBee GitHub App and the GitHub Action review and verify every pull request.
Install the IronBee GitHub App on your organization or account and pick the repositories. IronBee then reviews every pull request in them: a review with an inline comment on each finding and a suggested fix, a summary added to the pull request description, and the IronBee review check. Comment @ironbee-ai review on a pull 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 GitLab
Every merge request reviewed, with a pipeline status.
IronBee for Bitbucket
Every pull request reviewed, with a build status.
IronBee for Cursor
Verify what your Cursor agents ship, right inside the editor.