The PR lifecycle
The three states every open pull request falls into.
Every open pull request Angada tracks falls into exactly one of three buckets. They're checked in this order, so a PR that matches an earlier rule never falls into a later one.
Awaiting Author
The PR has a "changes requested" review on it — the author is the one who needs to act next.
Ready to Merge
The PR has all its required approvals, and CI has passed. Nothing is blocking it from being merged.
Needs Review
Everything else — including any PR that hasn't matched the two rules above. Draft PRs are never placed in this bucket; they're excluded from the lifecycle entirely until marked ready for review.
Flags that don't change the bucket
A few other badges can show up on a PR card alongside its bucket, but none of them move it into a different bucket:
- Stale — open longer than the configured threshold (3 days by default).
- Draft — not yet ready for review.
- CI status — pending, passed, or failed.
- Mergeable state — clean, conflicting, or unknown.
A PR can be Ready to Merge and still show a conflict badge — the badge just tells you something extra is worth a look; it doesn't reclassify the PR.
See The mental model for how the lifecycle fits with Reports and Connections, and Digests & reports for where these buckets show up in Slack.