Core Concepts
The mental model
How Workspaces, Reports, Connections, and Slack notifications fit together.
The one-sentence version
Angada watches the GitHub repos you connect, and turns what happens on them into Slack messages — a live-updating card per pull request, plus daily digests — scoped to the Reports and channels you set up.
How the pieces connect
Four pieces, in order:
- Workspace — your team's account in Angada, tied to your Slack workspace. Everything else lives inside one Workspace.
- Connections — which GitHub repos Angada can see, and which Slack channel each one routes to.
- Reports — a named group of GitHub authors whose open PRs get summarized together, on a schedule you pick.
- The PR lifecycle — every open pull request Angada tracks sits in exactly one of three states, which is what drives both the live card and the digests.
Put together: a repo is connected, routed to a channel; its pull requests move through the lifecycle; and a Report groups the people who own that work so their summary lands in one place, on schedule.
flowchart LR
Workspace --> Reports["Reports<br/>(who)"]
Workspace --> Connections["Connections<br/>(which repos, routed to which channels)"]
Connections --> Lifecycle["PR lifecycle<br/>(what state a PR is in)"]
Reports --> Slack
Lifecycle --> Slack["Slack<br/>(live PR cards + digests)"]