Pilotless vs GitHub scheduled reminders
TL;DR: GitHub's scheduled reminders send a Slack message, at times you choose, listing open pull requests in up to five tracked repositories, optionally only those where a review was requested [1][2]. They're built in and work well for "please review this". Pilotless answers a different question once a week: what's stuck across the repo, PRs and issues together. It's a free GitHub App that writes a weekly digest into one issue. Many teams should use both. Our stale pull requests guide covers setting them up alongside CODEOWNERS and a review norm.
Facts about scheduled reminders come from GitHub Docs, checked 2026-10-21. Sources are at the bottom.
At a glance
| Pilotless | GitHub scheduled reminders | |
|---|---|---|
| What it is | GitHub App that writes a weekly status digest | Built-in GitHub feature that posts pull request reminders to Slack [1] |
| What it covers | Weekly summary, Shipped, In flight, Closed and Who moved code; stalled PRs and unassigned issues under "Needs a decision or a nudge" | Open PRs in tracked repos; optionally only PRs with a review request [1] |
| Lists stalled PRs | Yes (open PRs with no activity for 7+ days) | Yes: open PRs filtered by "minimum staleness" in hours [1] |
| Lists unassigned issues | Yes (no assignee, quiet for 14+ days) | No (PRs only) [1] |
| Nudges inside the PR or issue thread | No (on the roadmap, not live) | No. Messages go to Slack [1] |
| Flags on unowned issues in their thread | No (on the roadmap, not live) | No |
| Slack | No (on the roadmap, not live) | Yes, and Slack is required [1] |
| Where it lives | One GitHub issue, updated in place each week | Slack messages |
| Cadence | Weekly | Any days and times you pick [1] |
| Coverage limits | Repos you install it on | Up to 5 repos per reminder and 20 oldest PRs per repo; add more reminders for more [1] |
| Setup | Install the App on chosen repos | Org owner authorises Slack, then team maintainers create reminders [1] |
| Price | Free | No separate price listed in the docs. Plan availability unverified [1][2][3] |
How they work
Scheduled reminders are configured per team, per organization or per person [1][2][3]. You choose a Slack channel, days and times, the repos to track, and filters: "require review requests", minimum age, minimum staleness, ignore drafts, ignore approved PRs, ignored terms, ignored or required labels, and "remind authors after reviews" [1]. "Require review requests" limits a reminder to PRs where a review was requested from the team or a team member; without it, all open PRs in the tracked repos are included [1]. Personal reminders can also send real-time Slack alerts [3]. That's a built-in way to keep review requests from being forgotten.
What they don't do: they don't look at issues, they post to Slack only, and each reminder covers at most five repositories [1]. A Microsoft study found that, of 200 PRs open 14+ days, 130 were waiting on the author (Maddila et al.) [6]. Reminders can include such PRs if you don't require review requests and turn on "remind authors after reviews".
Pilotless reads repo activity, and once a week it updates one GitHub issue titled "pilotless: weekly status": a summary line (commits, people, PRs merged, issues closed and opened), then Shipped, In flight, Needs a decision or a nudge, Closed, and Who moved code (per-author commit counts). "Needs a decision or a nudge" lists stalled PRs (open, no activity for 7+ days) and unassigned issues (no assignee, quiet for 14+ days) [4][5]. It doesn't need Slack. Nudges and flags inside each PR or issue thread are on the roadmap, not live.
Bottom line: reminders put open PRs in Slack on your schedule. Pilotless puts stalled PRs and unassigned issues in one GitHub issue once a week.
Pick GitHub scheduled reminders if…
Your team uses Slack and the main gap is reviewers forgetting requests.
You want reminders daily or several times a day [1].
You track five or fewer repos per team, or don't mind adding reminders [1].
You want something built into GitHub with no extra App.
Pick Pilotless if…
You also need unassigned issues in view, not just PRs.
You don't use Slack, or don't want status living in chat.
You want the weekly status in GitHub, in an issue you can link to.
You want issues and PRs in the same weekly list.
Using both (our recommendation)
Set up CODEOWNERS so every PR gets a named reviewer (free for public repos; private repos need GitHub Pro, Team or Enterprise [7]).
Turn on scheduled reminders for each team, with a minimum staleness of about 24 hours (our opinion; the Microsoft Nudge system only nudged after 24 hours without activity [6]).
Install Pilotless for the weekly digest of stalled PRs and unassigned issues.
The step-by-step is in our stale pull requests guide.
FAQ
Does Pilotless post to Slack like scheduled reminders?
No. Slack is on the roadmap, not live. Today the digest is a GitHub issue.
Does Pilotless comment on the PR itself?
Not yet. In-thread nudges are on the roadmap, not live.
Sources (all accessed 2026-10-21)
GitHub Docs, "Managing scheduled reminders for your team": https://docs.github.com/en/organizations/organizing-members-into-teams/managing-scheduled-reminders-for-your-team
GitHub Docs, "Managing scheduled reminders for your organization": https://docs.github.com/en/organizations/managing-organization-settings/managing-scheduled-reminders-for-your-organization
GitHub Docs, "Managing your scheduled reminders": https://docs.github.com/en/subscriptions-and-notifications/how-tos/managing-your-scheduled-reminders
Pilotless homepage: https://pilotless.nl/
Pilotless install page: https://pilotless.nl/install
Maddila et al., "Nudge: Accelerating Overdue Pull Requests Towards Completion": https://arxiv.org/abs/2011.12468 (200 PRs open 14+ days, 130 waiting on the author; nudges sent only after 24 hours without activity)
GitHub Docs, "About code owners" (plan availability): https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
Not verified: which GitHub plans include scheduled reminders. The three docs pages don't say.
Geekbot, Standuply, Range, Steady, Status Hero, LinearB, Swarmia and GitHub are trademarks of their respective owners. Pilotless is not affiliated with them.