FAQ
Common questions, answered.
Why isn't @-mention pinging the right person?
Either the GitHub login involved doesn't have an Identity Link to a Slack user yet — so it renders as plain text — or the channel has mentions turned off, which delivers the full living PR card without any @mention.
Why don't I see a repo in Angada?
Connected repos mirror your GitHub App's install access exactly. If a repo is missing, change what the App can access on GitHub's side (not in Angada), then let Angada re-sync.
Why did my digest not post today?
Check the digest's configured schedule and timezone first. If those look right and it's a Personal digest, remember it only sends when you actually have something pending — no open PRs authored by you and nothing awaiting your review means no DM that day.
I can't sign up from my region — why?
Self-serve account creation is currently blocked in a small set of regions pending regulatory clearance. This only applies to creating a brand-new account — it never affects signing back in to an account you already have, from anywhere.
What's the difference between a Report and a Channel Digest?
A Report is scoped by author — the GitHub usernames you add to it. A Channel Digest is scoped by repo routing — every PR in the repos routed to that channel, regardless of who the author is. They can overlap, but they're built from different sets.
Can one repo post to more than one channel?
Yes — see Channel routing. A repo can be routed to several channels at once; each gets its own copy of that repo's living PR cards and digests.
Does a review verdict mean the PR should be merged?
No — an Angada verdict is decision support: a structured read of the diff with evidence-linked findings. GitHub's review decision, your CI status, and your team's merge call remain separate signals, and the final decision is always yours.