Automated GitKraken Pull Request Queue
Every hour, WebRun opens GitKraken, lists the open pull requests across your repositories, works out which reviewer each one is waiting on and how long it has sat there, holds review time in Google Calendar for anyone with a backlog, and WhatsApps the team the oldest requests.
How do I stop pull requests sitting unreviewed all day?
Every hour, WebRun opens GitKraken, lists the open pull requests across your repositories, and works out who each one is waiting on and for how long. It holds review time in Google Calendar for reviewers with a backlog and WhatsApps the team the oldest requests still untouched.
- No pull request sits untouched through a whole working day
- Each reviewer sees only their own queue, grouped by age
- Requests with merge conflicts or no reviewer are flagged immediately
Built for engineering managers · team leads · software teams · open source maintainers
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.gitkraken.comin a real browser with your saved login - no setup, no API keys. -
1
GitKraken - list open pull requests by reviewer
WebRun opens GitKraken to list open pull requests by reviewer. - Open GitKraken and list the open pull requests across your repositories
- Capture the author, the requested reviewers, the repository, and the branch for each
- Work out how long each request has been open and how long since the last review activity
- Flag any request with merge conflicts or with no reviewer assigned at all
Done when Every open pull request has a reviewer, an age, and a blocked or waiting status.
-
2
Google Calendar - hold review time
WebRun opens Google Calendar to hold review time. - Add a short private review block to your own Google Calendar when the queue passes the size you set
- Put the repository names and the count of waiting requests in the event title
- Place the block in the next free slot in the working day
- Leave the event with no attendees. WebRun never sends a calendar invite to a teammate
Done when A private review block exists whenever the queue is above your threshold.
-
3
WhatsApp - nudge on the oldest requests
WebRun opens WhatsApp to nudge on the oldest requests. - Send your engineering chat in WhatsApp the requests waiting longer than your threshold
- Group them by reviewer so each person sees only their own queue
- Say how many hours each has waited and flag anything with merge conflicts
- Leave reviewing, approving, commenting, and merging to people. WebRun never touches a pull request
Done when The team has the current review queue grouped by reviewer.
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, comment on, or merge pull requests?
No. WebRun only reads the state of each pull request and reports the queue. Approving, commenting, and merging stay with your engineers, so no code moves without a human review.
Will it message reviewers individually?
No. It posts one grouped list to your own engineering chat in WhatsApp so people see their queue in context. It never sends a direct message to a reviewer or a calendar invite.
How does it decide a pull request is stale?
It measures time since the last review activity against the threshold you set, for example four hours, and lists only the requests past it so the hourly message stays short.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.