Guide

GitHub Scheduled Reminders: what they do, and where they stop

GitHub's built-in reminders are a fine start — a Slack ping about pull requests waiting on your team. Here is what they cover, the limits teams hit, and what to add when a ping is no longer enough.

What Scheduled Reminders give you

Scheduled Reminders are configured per organization or per team in GitHub settings. On a schedule you choose (say, every weekday at 9:00), GitHub posts a message to one Slack channel listing pull requests waiting on review from that team. Personal reminders can also DM you about reviews you were asked for. They are free and require no third-party app.

The limits teams run into

  • A message is not an overview. The reminder scrolls away with the rest of Slack. There is no page you can open at standup that shows every open PR and what each one is waiting for.
  • No time-in-state. A PR that has waited twenty minutes and one that has waited four days look the same in the list. Nothing escalates; nothing is flagged as stale.
  • Review-queue only. Reminders cover PRs awaiting review. Approved-but-unmerged work, drafts that quietly went stale, and changes-requested PRs sitting with the author are out of scope.
  • Team-by-team configuration. Each reminder is tied to one team and one channel. A lead who wants one picture across several repositories and teams has to assemble it by hand.
  • No SLA concept. You cannot say "reviews in this repo should start within 24 hours" and have anything enforce or even measure it.

What Gitboard adds

Gitboard keeps the Slack digest — and puts a live board behind it. Every open PR sits in a column for its actual state: draft, awaiting review, changes requested, approved but unmerged. Each card shows how long it has been stuck and who it is waiting on. Set an SLA per column and breaches get flagged on the board and in the digest.

The GitHub App is read-only — Gitboard never writes to your repositories. Pricing is flat per team, not per seat, and one repository is free forever.

Try Gitboard free

When built-in reminders are enough

Honestly: a small team with one repository and a fast review culture may never need more than the built-in reminders. Reach for a board when PRs regularly wait more than a day, when work spans several repositories, or when "what's blocking the release?" is a question someone asks out loud every week.