Automated Code Climate Coverage Alerts
Every weekday morning, WebRun signs in to Code Climate, reads the test coverage percentage for each repository, records it in Airtable next to yesterday's figure, and writes a Notion page listing every repository that dropped below your coverage threshold or fell more than your allowed daily slip.
How do I get alerted when test coverage drops in Code Climate?
WebRun signs in to Code Climate every weekday morning and reads the test coverage percentage for each repository you track. It logs the figure and the daily change into Airtable, then writes a dated Notion page naming every repository that fell below your threshold, tagged to the team that owns it.
- Coverage slides are caught the next morning, not at release time
- Every repository has a dated coverage history in one table
- Write-ups reach the owning team, tagged, only when something breaches
Built for engineering managers · platform teams · QA leads · development agencies
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
codeclimate.com/loginin a real browser with your saved login - no setup, no API keys. -
1
Code Climate - read coverage per repository
codeclimate.com
WebRun opens Code Climate to read coverage per repository. - Sign in to Code Climate and open the list of repositories you track
- Read the current test coverage percentage on each repository
- Note the maintainability letter alongside it so both signals sit together
- Compare with the previous run and calculate the change for each repository
Done when Every tracked repository has today's coverage figure and its daily change.
-
2
Airtable - log the daily figures
airtable.com
WebRun opens Airtable to log the daily figures. - Append one row per repository per day to your coverage table
- Fill in the date, the coverage percentage, the maintainability letter, and the daily change
- Set a status of healthy, watch, or below threshold using the limits you configured
Done when Today's coverage figures are logged with a status on every repository.
-
3
Notion - write up the repos that slipped
notion.so
WebRun opens Notion to write up the repos that slipped. - Create a dated page in your engineering space for any repository below threshold or falling fast
- List the repository, the old and new coverage, and the size of the drop
- Tag the team that owns each repository so the page has a named reader
- Write nothing when every repository is healthy, so the space stays signal only
Done when Every slipping repository is written up and tagged to its owning team.
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
Does it touch my code or my pull requests?
No. WebRun reads the coverage and maintainability figures shown in Code Climate. It never comments on a pull request, never blocks a merge, never changes a repository setting, and never pushes code.
What counts as a drop worth writing up?
Two things you set: an absolute coverage floor per repository, and a maximum allowed daily slip. A repository breaching either one gets a Notion page. Everything else is logged in Airtable and left alone.
Will it spam Notion on a quiet day?
No. On days when every repository is healthy, WebRun writes nothing to Notion at all. Only the Airtable log gets a row, so the presence of a page always means something actually slipped.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.