Review LedgerLive
One living record per pull request.
Every finding keeps an ID and a state across pushes: open, fixed, disputed or accepted. The same commit under the same policy gets the same verdict, and the check says exactly which commit it judged.
How it works
Step by step.
One record per PR: every finding keeps its ID across pushes.
- 01First reviewFindings get stable IDs from their content and place, not from the comment that carries them.
- 02You pushAn incremental review reads only what changed since the last judged commit.
- 03Threads settleFixed findings reply and resolve themselves; nothing is ever posted twice.
- 04Verdict at a SHAOne check run per head commit, updated in place, so the merge box shows the current answer.
In detail
What it does, exactly.
- A verdict belongs to a commit, so a stale approval of old code is visible.
- Findings carry state, so 'is this fixed?' has one answer.
- On GitHub
- One check run per head SHA, resolved threads, @forseti explain
- In the dashboard
- PR timeline, finding states, audit log
Never repeat
A finding already raised on this PR is not raised again, even after the code around it moves.
Explain in the thread
Reply @forseti explain on a finding and get the reasoning in that thread, free to you, with limits per PR and per day.
Full timeline
The dashboard shows every run on the PR, what it cost, what it found and what changed state.
Audited
Feedback, manual triggers, policy and cap changes are written to the workspace audit log.
Works with
Next: Team memory & precisionPut 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.