Notifications introduction
Angada's coordination layer — living PR cards, routing, digests, and the attention loop.
Reviews are only half of Angada. The other half is making sure the right person acts at the right time. Angada's notifications turn pull-request activity into a coordination loop: every PR has one live source of truth in Slack, every team member knows what's waiting on them, and managers can see where review work is piling up.
One living card per PR
Every pull request in a connected repo gets a living card — a single Slack message, updated in place as the PR changes, instead of a fresh message for every event. The card and its thread carry the PR's state, CI progress, review requests, comments, and merge/close updates. See Living PR card.
Routing and delivery
Where cards land is up to you, and everything here rides on the two integrations — the GitHub App that watches your repos and the Slack workspace where updates post:
- A Workspace-wide default channel catches everything without setup.
- Per-repo routes send a repo's activity to specific channels — a squad channel, a firehose, a leadership view.
- Delivery filters per route: human-only delivery, bot handling, comment delivery, and an author denylist.
See Channel routing.
Mentions that reach a person
When a PR is blocked, Angada mentions whoever needs to act — but a mention only pings if Angada knows which Slack user owns the GitHub login. Identity links connect the two, matched automatically by email or set manually.
The dashboard: what needs attention
The Angada dashboard groups every tracked PR into Needs review, Awaiting author, and Ready to merge, with ownership, CI, conflicts, and staleness on each item. The attention queue surfaces the stalled PRs specifically — what's stuck, why, and on whom. When a PR is stalled, an admin can send a nudge: a Slack ping under the living card, limited to once per PR per workspace-local day.
Scheduled summaries
Three scheduled messages keep the loop honest without anyone watching a feed:
- Personal digests — a private DM of what's waiting on you. Personal and channel digests
- Channel digests — a daily rollup per channel. Personal and channel digests
- Team Reports — a scheduled summary for a chosen set of authors. Team Reports
Needs review / Awaiting author / Ready to merge buckets, with the attention queue beside them.
Seeing the system, not just the PRs
Two views answer management questions the cards can't:
- Reviewer load — is review work spreading fairly, or piling onto one person? Reviewer load
- Review SLA — are reviewers responding within the team's target, by priority tier? Review SLA