GitHub integration

GitHub Integration

Install the app once and every pull request gets driven. IronBee reads what the commit changed, exercises it against the deployed preview, and posts what it found on the pull request itself.

Install the GitHub AppRead the docs

Connect GitHub. Every pull request gets verified.

  1. A commit landsOn a pull request, or when one is opened. No workflow file to add.
  2. Change analysedIronBee checks out the code, reads what the commit changed and decides what to check.
  3. Driven in a real browserAgainst your real backend, on the build that pull request produced. Watch it live in the Console.
  4. Verdict on the pull requestPosted as a check and a comment: what was verified, what was found, and the fix on the line.

Install the app once. From then on every pull request is verified before anyone reviews it, and the evidence lives in the Console.

On the pull request

The whole run, in the review

No tab to open and no dashboard to check. What the agent did, what it found, and where it came from are in the thread with the change.

ironbee-aiBotcommented 2 days ago

IronBee Verification

Verification failed
What was verified
  • Signed in and added a $42 item to the cart.
  • Applied the percent coupon TARE10 and compared the cart against the real Stripe Checkout session.
  • Checked out with no coupon and compared the displayed total against the amount actually charged.
What was found
  • lib/coupons.ts divides by 10 instead of 100, turning every percent coupon into an effective 100% off. TARE10 discounted the full $42 to $0.00 in the real Stripe session, not just in the UI.
  • The cart still shows a $9 shipping line and a $51 total, but checkout charges $42. The amount shown to the customer no longer matches the amount taken.
Issues 2Important files changed 3
Access

Read-only, and only while a run is happening

The app asks for what the verification agent needs to do its job and nothing beyond it.

01

Read-only repository access

The agent checks out your code during an automated verification. It does not write to your repository.

02

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.

03

Findings, not code, leave the run

What lands on the pull request is the verification: what was checked, what broke, and the files involved.

Now generally available

Ready to ship
AI-generated code with confidence?

Create your account and start verifying what your agents ship. Catch regressions before they reach production.

No credit card required.