How to Get Stale Pull Request Reminders in Slack

Stale pull requests sit because nobody is nudged. Here is how to send a Slack pull request reminder that flags what has gone quiet, across every repository.

August 20, 2026

A pull request goes stale the moment it drops off everyone's screen. The author is waiting on a review, the reviewer never reopened the GitHub tab, and the PR sits for three days until it surfaces in standup. Nothing is blocked by code. It is blocked by attention.

The fix is a reminder that names what has gone quiet and sends it somewhere people already look, which is Slack. This post covers what GitHub can and cannot do for stale pull requests, then how to get a Slack pull request reminder that flags the ones rotting across all your repositories.

What makes a pull request stale

Stale means no activity for a while: no new commits, no comments, no reviews. Most teams treat 24 to 48 hours of silence as the threshold. A draft that is still being written is not stale. A PR that was approved and is waiting to merge is not stale either. The ones worth chasing are open, reviewable, and untouched.

Stale PRs cost more than the review itself. The branch drifts from main, so the author rebases and re-tests. Context evaporates, so the reviewer has to reload the whole change from scratch. A one-day review that slips to five days is a slower, riskier review.

Can GitHub remind you about stale pull requests?

Partly. GitHub has a built-in scheduled reminder that posts open pull requests to Slack at times you choose. The personal version, under Settings, Integrations, Scheduled reminders, has no staleness filter at all. It lists review requests assigned to you and stops there.

The team version does more. Buried under a team's Settings tab, it exposes minimum age and staleness in hours, ignored and required labels, exclude draft pull requests, and ignore approved pull requests. That is a real stale filter. The catch is where it lives and how far it reaches. The full walkthrough is in our guide to GitHub scheduled reminders.

The hard limit is repositories. Each reminder fires for up to five repositories, either five you pick or the five with the oldest average PR age. The moment your stale PRs are spread across more than five repos, you are hand-maintaining several reminder configs to see them all.

The gap: no cross-repo view of what is rotting

GitHub's model is repository-first. Reviewers think person-first. You do not care which repo a stale PR lives in, you care that it is waiting on you or on someone you can nudge. GitHub makes you enumerate repositories instead of just asking "what is stale and assigned to me, everywhere?"

The personal reminder has no staleness threshold.
The team reminder has one, but caps at five repositories per config.
Neither gives a single "everything stale and waiting on me" digest.
A stale PR still needs someone to actually ping the reviewer or author.

Flag stale PRs in Slack with GitNotifier

GitNotifier sends a scheduled Slack digest that queries by person, not by repository. It pulls everything assigned to you (assignee:@me) and everything requesting your review (review-requested:@me) across every repository you can see, with no five-repo cap. For a side-by-side of the native reminder, Zapier, and a person-centric digest, see our GitHub pull request digest for Slack guide.

The parts that matter for stale pull requests:

Stale flagging: any pull request with no activity for 24 hours is marked in the digest, so what is rotting is obvious at a glance.
Author mentions: PR authors who are in your Slack workspace get an @-mention, so a stale PR reaches a real person instead of a silent line item.
Draft exclusion by default, so work-in-progress never gets flagged as stale.
Up to four reminder times a day, daily, weekdays, or weekly on Monday, so a PR cannot sit quiet for long.
An optional section for your own PRs awaiting review, so you can chase the reviewers sitting on your work too.

Tip: keep GitHub's team reminder for one busy repository if you like its staleness filter, and let GitNotifier cover the cross-repo "what is stale and waiting on me" view. They do not conflict.

Set it up in Slack

Setup is a Slack modal, not a five-level menu dive. Open the GitNotifier App Home, click Configure reminders, pick your cadence and up to four times, and send a test. Your timezone comes from your Slack profile automatically. Full steps live in the GitHub PR notifications for Slack guide, and every Slack notification option for GitHub weighs the full landscape if you want to compare first.

Frequently asked questions

What counts as a stale pull request?

A stale pull request is one that has had no activity, no new commits, comments, or reviews, for a set period. Teams commonly draw the line at 24 or 48 hours. Past that point the PR is waiting on a person who has forgotten it, not on more work.

Can I get a Slack pull request reminder for stale PRs?

Yes. GitHub's team scheduled reminders can filter by minimum age and staleness in hours and post to Slack, but they cap each reminder at five repositories. GitNotifier sends a person-centric PR Review Digest to Slack that flags any PR with no activity for 24 hours across every repository you can see.

Does GitHub remind you about stale pull requests automatically?

Not on its own. GitHub's inbox does not chase you, and the personal scheduled reminder has no staleness filter. Only the team reminder exposes minimum-age and staleness options, and it lives several levels deep in team settings.

How do I nudge the reviewer of a stale pull request?

GitNotifier @-mentions the PR author in the Slack digest when they are in your workspace, so a stale PR reaches a real person instead of a silent list. You can also reply in-thread to ping the reviewer directly.

Stop pull requests from going quiet

GitNotifier flags every stale pull request in one Slack digest, across all your repositories, up to four times a day, and @-mentions the person who can move it. No five-repo cap, no buried settings.

View all articles