Automated Codecov Coverage Drop Alerts
Every hour, WebRun opens Codecov, checks open pull requests for a coverage drop below your team's threshold, posts the list to Telegram naming the pull request and how many points coverage dropped, and texts the pull request author through Twilio when the drop is 5 points or more so a real coverage regression gets fixed before merge.
How do I catch test coverage drops before a pull request merges?
WebRun checks Codecov every hour for pull requests where test coverage drops below your threshold, posting the list to Telegram with the author and point change. Drops of 5 points or more also get a direct text to the author through Twilio, so a real coverage regression gets fixed before it merges.
- Coverage regressions get flagged before merge, not after
- Big drops reach the author directly instead of waiting in a list
- The coverage threshold is enforced every hour without a manual check
Built for engineering teams · tech leads · QA engineers · software development 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.codecov.io/loginin a real browser with your saved login - no setup, no API keys. -
1
Codecov - find pull requests with a coverage drop
- Open Codecov and check open pull requests for their coverage change
- Capture the pull request, author, and coverage point change for anything below threshold
- Separate out drops of 5 points or more
Done when Every open pull request below the coverage threshold is listed with its point drop.
-
2
Telegram - post the list to the team
telegram.org
WebRun opens Telegram to post the list to the team. - Post the list of pull requests below threshold to the team channel
- Show the author and coverage point change for each
- Note which ones are also being texted to the author directly
Done when The team channel has today's list of pull requests below the coverage threshold.
-
3
Twilio - text the author on a big drop
twilio.com
WebRun opens Twilio to text the author on a big drop. - Text the pull request author directly for drops of 5 points or more
- Name the pull request and the coverage point change
- Skip the text for smaller drops. Those stay in the Telegram list only
Done when Every author with a 5 point or larger drop has a text.
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 block the pull request from merging?
No. WebRun only reports the coverage drop. Blocking or approving a merge is always your team's own review process.
What counts as a threshold worth flagging?
You set the coverage threshold. Any pull request that falls below it lands on the Telegram list, with a text reserved for drops of 5 points or more.
Does it check every commit or just the final one?
It checks each pull request's current coverage against the base branch every hour, so the number reflects the latest commit each time.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.