Changelog
What’s new in Angada
Every Angada release and improvement, newest first. Subscribe to the RSS feed or check back after each ship.
AI Review reports findings with code evidence
Angada reviews pull requests on your connected repositories and reports each finding with file and line evidence, posted as a GitHub check your team already watches.
Angada's AI Review is available on every connected repository. Open a pull request and the Angada check starts reviewing — no new workflow to learn, no commands to run.
When the review finishes, the check reports findings with a claim, severity, confidence, and the file and line evidence behind each one, so you can verify every report against the diff before you act on it. The review status stays separate from GitHub's approval state: Angada describes its own review result and never approves or requests changes on your behalf.
- Understand a review — verdicts, findings, and code evidence: Understand a review.
- Keep reviews current — reviews re-run as pull requests update, and findings carry forward: Re-runs and continuity.
- Tune what runs — draft and bot policies, caps, and eligibility: Review settings.
Living PR cards keep Slack channels current
Each pull request gets one Slack message per routed channel, edited in place as the PR moves through review — so the channel shows current state instead of a scroll of duplicates.
Notifications deliver one live-updating Slack message per pull request per routed channel — the living PR card. Instead of posting a new message for every event, Angada edits the same card in place as the PR progresses, so the channel always shows current state.
The card and its thread carry the full pull request lifecycle: state, CI progress, review requests and verdicts, new comments, and the merge or close outcome. Reviewers, assignees, and mergeable state update directly on the card, and whoever is blocking the PR can be pinged through a linked Slack identity.
- One card per PR — how the card updates through a PR's life: Living PR card.
- Route the right repos — send each repository's cards to the channels that need them: Channel routing.
- Ping the blocker — link GitHub and Slack identities for real @mentions: Identity links and mentions.