Merge readinessLive
One place that answers “can this merge?”
For every open PR: conflicts, CI, approvals, approvals that went stale after a push, how long it has waited, and Forseti's own verdict next to CI. Daily or weekly digests go to Slack or Teams.
Readiness · open PRs
Example
| PR | Conflicts | CI | Approvals | Waiting | Forseti |
|---|---|---|---|---|---|
| #518 Refund partial orders | None | Pass | 2 | 3h | clear |
| #512 Session expiry from settings | None | Pass | 11 stale | 26h | 1 blocking |
| #509 Bulk import for SKUs | Yes | Fail | 0 | 51h | 2 should fix |
Weekly digest → #eng-reviews (Slack)Send test
How it works
Step by step.
Conflicts, CI, approvals and Forseti's verdict in one place.
- 01WatchMergeable state, checks state, approvals and the last activity for each open PR.
- 02Spot stale approvalsAn approval given before the latest push is marked stale.
- 03BoardThe Readiness board lists blockers per PR, oldest wait first.
- 04DigestSend a daily or weekly digest to a Slack or Teams incoming webhook, with a Send test button.
In detail
What it does, exactly.
- Stale approvals are called out, because approving old code is not approving the PR.
- On GitHub
- Verdict per head SHA
- In the dashboard
- Readiness board, digests
Forseti's verdict beside CI
The review verdict for the head commit sits next to the checks, so one row answers the question.
Review lag
Hours since the PR last moved, so nothing waits quietly.
Slack and Teams: ready
Digests use incoming webhooks. Connect one in Integrations.
No new permissions
Readiness reads pull requests, checks and reviews with the access Forseti already has, refreshed every 15 minutes.
Works with
Next: IntegrationsPut 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.