Remind Engineers About Stale PRs
Every morning, WebRun opens GitHub and scans open pull requests across your repos, identifies any that have had no activity for more than your configured threshold, and posts a Slack message tagging each author so they can push things forward.
How can I automatically remind engineers about stale pull requests?
Every morning, WebRun opens GitHub, scans open pull requests across your repos for any that have had no activity beyond your configured threshold, and posts a Slack message tagging each author - so review bottlenecks are surfaced and resolved before they block your team's work.
- Stale PRs surfaced daily before they block downstream work
- Authors nudged automatically without a manager manually chasing
- Review cycle time reduced by eliminating silent bottlenecks
Built for engineering managers · DevOps engineers · software engineering teams · tech leads
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
github.comin a real browser with your saved login - no setup, no API keys. -
1
GitHub - scan for stale open PRs
github.com
WebRun opens GitHub to scan for stale open PRs. - Open the Pull Requests tab in each configured repository
- Filter to open PRs and sort by 'Last updated' ascending
- Flag any PR where the last commit or comment is older than your staleness threshold (default 3 days)
- Capture the PR title, author, reviewer(s), and days since last activity
Done when Every stale open PR is identified with its author, reviewer, and inactivity period.
-
2
Slack - nudge authors and reviewers
slack.com
WebRun opens Slack to nudge authors and reviewers. - Post a daily digest to #engineering listing each stale PR with a link and the days-idle count
- Group by repository for readability
- Tag the PR author and assigned reviewer for each item
Done when Authors and reviewers have been notified about every stale PR.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it close stale PRs automatically?
No - closing a PR is irreversible and requires a human call. WebRun only notifies; you decide what to merge, request changes on, or close.
How do I set the staleness threshold?
You set the number of idle days in the plan - the default is 3, but you can make it tighter or more relaxed to match your team's rhythm.
Can it cover multiple repositories?
Yes. List as many repos as you like and they all appear in one consolidated digest each morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.