← All steps
Step 04
Review
Suggested code arrives as a PR. You remain the editor-in-chief.
github.com/acme/payments-api
2 files · +2 −2
@@ src/billing.ts @@ confirm() −1 +1
return stripe.paymentIntents.confirm(id, {
- api_key: process.env.STRIPE_KEY,
+ stripeAccount: process.env.STRIPE_KEY,
})
@@ src/webhooks.ts @@ constructEvent() −1 +1
- stripe.webhooks.constructEvent(body, sig, secret)
+ stripe.webhooks.constructEventAsync(body, sig, secret)
Opening pull request…
In one sentence
A pull request is opened. Your team merges it.
You control
What actually lands in the repo.
For everyone
Versionly never ships to production on its own. A person on your team reads the change and clicks merge — or asks for edits.
For engineers
A focused pull request lands on the default branch workflow. Review, request changes, or close it.
What happens
- A suggested patch is opened as a GitHub pull request.
- Your existing review rules still apply.
- Merge when it looks right. Ignore it if it does not.