Team Reports
Group a set of GitHub authors and summarize their open PRs on a schedule.
A Report groups a set of GitHub authors together so their open pull requests get summarized in one scheduled Slack message, posted to a channel you pick. You can have more than one Report — for example, one per squad — each with its own members and its own schedule.
Creating a Report doesn't change who can see what in GitHub; it only decides whose PRs are counted together for that summary. Reports are also the scope for reviewer load analysis and review SLAs.
Create a Report
- Open Reports and select Create Report (or Create your first Report on an empty Workspace). Enter a name and timezone, then confirm.
- On the new Report's Authors tab, add the GitHub usernames whose PRs should count toward this Report, one at a time.
- On the Schedule tab, set the Slack channel this Report should post to, confirm its timezone, and choose the times of day it should post.
The Report's post in its channel with open, merged, and attention sections.
What posts to Slack
At each scheduled time, the Report posts a message to its channel listing every tracked author's open PRs, grouped by lifecycle state — Needs Review, Ready to Merge, or Awaiting Author. See Personal and channel digests for a section-by-section reading guide; the layout is the same.
A Report's digest 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.