Skip to content
Language

Merge without
the guesswork.

Pull requests pile up and bugs still slip through. EasyMerge reviews every one, points to the lines that need work, and tells you plainly if it is safe to merge.

Where EasyMerge fits

Why teams choose EasyMerge for faster, clearer pull-request reviews.

No per-seat fee. Extra credits when you need them.

One plan covers the whole GitHub organisation. Add review credits whenever your team needs more.

Live in the dashboard. Findings appear as they arrive.

Watch the review run, read every finding there.

Dependabot alerts in one view. Prioritise the risks that need action.

Use Security Center to follow affected dependencies, fix pull requests and repository checks.

Pro feature

Spec review. Catch code that contradicts your specs.

Compare relevant code changes with Markdown, text, YAML or JSON specifications.

One review, two views

Read the review the way you work

Same findings, same GitHub review. Switch any time.

#142Add retry logic to Stripe webhook handler

jane-dev · jane/webhook-retry → main · updated 2h ago

deepsecurity

CompletedLow confidence 4.6/101 critical1 warning1 info0/3 handledNew commit a1b2c3d · 2/3 files · 1 skipped · 2m 14s

Review summaryRetry logic is sound, but two things need attention before merge: the backoff has no jitter, so concurrent retries will keep colliding, and the handler still acknowledges the webhook before the retry queue accepts the job — a crash in between drops the event silently.

Filter files /

Files with findings 2

stripe.handler.ts src/webhooks

stripe.handler.test.ts src/webhooks

Skipped 1

src/webhooks/stripe.handler.ts+34−6reviewed

warningline 59 · posted 2h ago

@@ -54,9 +54,9 @@ export async function stripeWebhookHandler(req: Request, res: Response) {

54 const event = req.body;
55− await retryWithBackoff(() => processEvent(event));
55 const isValid = verifySignature(req.headers['stripe-signature'], req.rawBody);
56 if (!isValid) {
57 return res.status(400).send('Invalid signature');
58 }
59+ await retryWithBackoff(() => processEvent(event));

Signature verification happens after the retry loop starts. Move it before any retry so an invalid signature fails fast instead of consuming retry budget.

What you get

Everything below works out of the box once the GitHub App is installed.

Open a pull request; the review starts on its own, and again on every push

OpenAdd retry logic to Stripe webhook handler #142
  1. Jjane-dev opened this pull request

Reviews start from the PR events you choose

How a review happens

Four steps, and only the first two need you.

01

Sign in with GitHub

Authorize EasyMerge and install the GitHub App on the account or organization you want reviewed.

02

Pick your repositories

Grant access to selected repositories, or all of them. They appear in the dashboard after you sync.

03

Open a pull request

GitHub notifies EasyMerge and the review starts automatically; there is no button to press.

04

Read the review

One GitHub review is posted, its body summarising the result and every finding attached to the line it refers to.

Help when a review looks wrong

The EasyMerge support team is one ticket away; open it from Help & Support in the dashboard sidebar.

First reply

24h

Counted around the clock, not business hours. We raise the priority ourselves when something is broken in production.

  • Urgent2h
  • High8h
  • Normal24h
  • Low48h

Filed with its context

Report a problem from a review or a repository and it arrives with both attached; no need to explain where to look.

Screenshots and logs welcome

Up to five files per message, 10 MiB each. Paste a screenshot straight into the reply box.

Open until it is solved

Anyone on the installation can reply, and the bell tells you the moment support answers.

Read the support guide

Ready to review?

Select your repo and begin the work right away!