Glossary
Every term Angada uses, in the words you see on screen.
Workspace
Your team's account in Angada, tied to a single GitHub account and a single Slack workspace. Everything else — connected repos, Reports, members — lives inside one Workspace.
Report
A named group of GitHub authors whose open pull requests are summarized together in a scheduled Slack message.
Member / Admin
Anyone signed in to your Workspace is a member. An admin can additionally manage Workspace settings, connect or disconnect integrations, and invite other members.
Connected repository
A GitHub repo Angada can see, mirrored from your GitHub App installation's access — added or removed on GitHub's side, not Angada's.
Living PR card
The single Slack message that represents a pull request in a channel — posted once and updated in place as the PR changes, rather than re-posted for every event.
Channel routing
Sending a connected repo's notifications to a specific Slack channel instead of the Workspace's default channel.
Identity Link
A connection between a GitHub username and a Slack user. Mentions only ping a real person when the GitHub login involved has a link — otherwise they render as plain text.
Blocker mention
An @mention in a living PR card for whoever is currently blocking it — a requested reviewer, or the author when changes are requested — shown only when that GitHub login has a linked Slack account and the channel allows mentions.
Report digest / Channel digest / Personal digest
Three scoped versions of the daily summary: a Report digest covers one Report's authors, a Channel digest covers every repo routed to one channel, and a Personal digest is a private DM of just your own open and pending PRs.
Needs Review / Ready to Merge / Awaiting Author
The three states every open pull request falls into: waiting on a reviewer, cleared to merge, or waiting on its author after changes were requested.
Finding
A single issue Angada's AI review raises on a pull request, anchored to the exact code it came from — with a severity, a confidence level, and file-and-line evidence you can open.
Verdict
Angada's overall judgment of a pull request after a review — for example, that it looks clear or needs a human look. It's decision support for your team; GitHub's own review decision and your merge decision remain separate signals.
Review Seat
An assignment that turns on Angada reviews for the pull requests one GitHub developer authors. It's separate from Workspace membership — being a member doesn't mean your PRs are reviewed, and being reviewed doesn't require an Angada login.
AI Wiki
A generated, navigable documentation site for one of your connected repositories, built from an index of the code and cited to the exact source files it describes.
Reviewer load (Concentrated / Overloaded)
How review work is spread across a team. Concentrated means one reviewer handles a disproportionate share over time; Overloaded means one reviewer currently has too many pending requests at once.
Review SLA
A configured first-response time target for reviewers, by priority tier, tracked as a weekly compliance percentage.
Plan (Free / Pro / Business)
The pricing tier your Workspace is on, which determines its repo, developer, and Report limits.
Trial
A temporary, full-featured period on the Pro plan with no payment required, before your Workspace settles onto a paid plan or Free.
Active developer
A distinct GitHub login that authored or reviewed a tracked pull request in the last 30 days — the measure your plan's developer limit is counted against.