Automated Bitbucket Stale Pull Request Alerts
Every morning, WebRun opens Bitbucket, finds pull requests with no review activity in the last 2 days, posts a nudge list to Slack ranked by how long each has waited, and separately pages the team's Telegram channel for anything stalled 5 days or more so old requests cannot hide in the queue.
How do I stop Bitbucket pull requests from stalling without review?
WebRun checks Bitbucket every morning for pull requests with no review activity, posts a ranked nudge list to Slack showing who has waited longest, and sends a separate Telegram escalation for anything stalled 5 days or more. Reviews get chased automatically instead of aging quietly in an open pull request queue.
- Pull requests get a nudge before they go stale, not after
- The oldest reviews stand out instead of scrolling past in Slack
- Nothing sits unreviewed for 5 or more days without a direct escalation
Built for engineering teams · tech leads · software development teams · platform teams
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
bitbucket.org/account/signinin a real browser with your saved login - no setup, no API keys. -
1
Bitbucket - find pull requests waiting on review
WebRun opens Bitbucket to find pull requests waiting on review. - Open Bitbucket and list open pull requests across the team's repositories
- Check each one's last comment or approval activity
- Flag any with no activity for 2 days or more, and separately any at 5 days or more
Done when Every pull request with no recent activity is listed with its age and reviewer.
-
2
Slack - post the daily nudge list
WebRun opens Slack to post the daily nudge list. - Post the day's nudge list to the review channel, oldest first
- Show the author, reviewer, and days waiting for each
- Note which ones are also being escalated to Telegram
Done when The review channel has today's ranked nudge list.
-
3
Telegram - page anything stalled 5 days or more
WebRun opens Telegram to page anything stalled 5 days or more. - Send a separate escalation message for pull requests stalled 5 days or more
- Name the author and reviewer so it is clear who to follow up with
- Skip any that were reviewed since the Bitbucket check ran
Done when Every pull request stalled 5 days or more has an escalation message in Telegram.
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 approve or merge anything?
No. WebRun only reports which pull requests are waiting. Reviewing, approving, and merging stay entirely with your engineers.
Why post to both Slack and Telegram?
Slack carries the full daily list for visibility. Telegram is reserved for the oldest, most stalled pull requests so they stand out instead of scrolling past in a longer list.
What counts as stalled?
No comment or approval activity for 2 days lands it on the daily list. No activity for 5 days or more also triggers the Telegram escalation.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.