Automated Codacy Blocked Pull Request Alerts
Every morning, WebRun opens Codacy, finds the open pull requests that are failing the quality gate, records the author, the repository, the failing check, and how long each has been blocked into Google Sheets, then sends the dev group a short WhatsApp list so blocked work does not sit for days.
How do I track pull requests blocked by Codacy quality gates?
WebRun opens Codacy every morning and finds the open pull requests failing your quality gate. It logs each one into Google Sheets with the author, repository, failing check, and days blocked, then sends the dev group a WhatsApp list led by the oldest, so blocked work gets unstuck the same day.
- Blocked pull requests are named every morning with their author
- The count of blocked work is trackable day against day
- Nothing sits failing a gate for a week unnoticed
Built for engineering managers · development teams · tech leads · 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
app.codacy.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Codacy - find pull requests failing the gate
codacy.com
WebRun opens Codacy to find pull requests failing the gate. - Sign in to Codacy and open the pull requests view across your repositories
- Collect every open pull request that is not passing the quality gate
- Record the repository, the author, the new issues found, and the coverage change
- Note how many days each pull request has been open and blocked
- Skip pull requests already merged or closed
Done when Every open pull request failing the gate is captured with its author and age.
-
2
Google Sheets - log each with its author and age
google.com
WebRun opens Google Sheets to log each with its author and age. - Open your engineering tracking sheet in Google Sheets
- Append today's rows: date, repository, pull request, author, failing check, days blocked
- Update the status of anything from previous days that has since passed or merged
- Keep the history so you can see whether the blocked count is trending down
Done when The sheet holds today's blocked pull requests and closes out yesterday's.
-
3
WhatsApp - nudge the dev group
whatsapp.com
WebRun opens WhatsApp to nudge the dev group. - Send the dev group a short WhatsApp list of what is blocked and who owns it
- Put anything blocked more than two days at the top
- Name the failing check in plain language so the fix is obvious
- Stay quiet on mornings when nothing is blocked
Done when Every blocked pull request has reached its author in WhatsApp.
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
Can it merge or approve a pull request?
No. WebRun reads the Codacy analysis and never merges, approves, or dismisses anything. It also never ignores an issue or changes a quality gate. Every code decision stays with your engineers.
Does it comment on the pull request?
No. The only message it sends is an internal WhatsApp list to your own dev group, plus rows in your own sheet. It leaves no comment on the pull request itself.
Will the same pull request be nagged about forever?
It reports what is still blocked each morning and marks anything merged or passing as resolved in the sheet, so a fixed pull request drops off the list the next day.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.