Automated Graphite Stuck Stack Chase Alerts
Every morning, WebRun opens Graphite, reviews stacked pull requests across your repositories, texts the reviewer when a stack has been blocked on their review for more than three days, and saves a weekly report of stuck stacks to Google Drive so a blocked stack does not hold up everything behind it.
How do I stop a stuck Graphite stack from blocking everything behind it?
WebRun reviews Graphite stacks every morning, and when one has been blocked on review for more than three days, texts the reviewer directly with the stack and how many pull requests wait behind it. It also saves a weekly stuck-stack report to Google Drive, so a blocked review does not quietly hold up everything stacked on top.
- A blocked stack gets a direct text within a day of stalling
- Reviewers see exactly how many pull requests are waiting on them
- A weekly record makes it easy to see if review bottlenecks are improving
Built for Engineering teams using stacked diffs · platform engineering teams · engineering managers · fast-moving product 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
app.graphite.dev/loginin a real browser with your saved login - no setup, no API keys. -
1
Graphite - review stacked pull requests
- Open Graphite and review stacked pull requests across repositories
- Check how long each stack has been waiting on its current reviewer
- Flag any stack blocked more than three days and note how many pull requests are stacked behind it
Done when Every blocked stack is identified with its reviewer and how many pull requests are waiting behind it.
-
2
Twilio - text the blocking reviewer
twilio.com
WebRun opens Twilio to text the blocking reviewer. - Send a text to the reviewer for each stack blocked more than three days
- Include the stack's top pull request and how many are stacked behind it
- Keep the message to a single line
Done when The blocking reviewer has been texted about every stack stuck more than three days.
-
3
Google Drive - archive the stuck-stack report
drive.google.com
WebRun opens Google Drive to archive the stuck-stack report. - Open the Stuck Stacks Reports folder in Google Drive
- Save a weekly report listing every stack that was blocked that week and how long it took to clear
- Keep the last eight weekly reports for trend comparison
Done when A weekly stuck-stack report is saved in Google Drive.
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 WebRun review or reassign the stack itself?
No. It only tracks how long a stack has been blocked and texts the current reviewer. Reviewing the code or reassigning it stays a human decision.
Why does a blocked stack matter more than a single blocked pull request?
Because every pull request stacked behind it is also blocked from merging, so the text includes how many are waiting to make the impact clear.
Does it text on weekends?
It checks every morning including weekends, but you can restrict it to business days in your run settings if that fits your team better.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.