Ask Forseti & release notesLive
Ask about a PR in plain English. Ship notes people read.
Ask why a change is safe, where a value comes from, or what breaks if it ships, and get an answer that cites file and line. When you release, turn merged PRs into notes grouped by Features, Fixes and Breaking.
finally block releases it on every path, including the throw from reserveStock.allocate.ts:34allocate.ts:52Features · Partial refunds keep the rest of the order open.
Fixes · Stock is no longer double-allocated when two checkouts overlap.
Breaking · The refund webhook now sends amounts in pence.
How it works
Step by step.
Ask about a PR in plain English; draft notes for a range.
- 01Ask in the dashboardA chat drawer on PR detail streams answers with file:line citations.
- 02Or on GitHub@forseti ask <question> replies in the thread.
- 03Notes per PREach review already carries a one-line release note.
- 04Notes per rangePick a repo and two refs; merged PRs become notes grouped Features / Fixes / Breaking. Copy as Markdown.
In detail
What it does, exactly.
- Answers cite the code they rely on, so you can check them in a click.
- On GitHub
- @forseti ask, @forseti release-notes
- In the dashboard
- Ask drawer on PR detail, release notes
Metered, tiny
Questions are charged as a small credit amount, shown in the ledger like everything else.
History kept
The conversation stays with the PR, so the next reviewer can read it.
@forseti release-notes
Ask on a PR and the notes are posted there.
Written for users
Notes describe what changed for the people using the product, not the commit messages.
Put Forseti on your next pull request.
Connect GitHub in four clicks. Your first review starts by itself on your latest small open PR, priced before it runs.