All templates

Automated Codecov Missing Upload Alerts

Every morning, WebRun opens Codecov, checks each repository for a recent coverage upload, finds the ones that have gone silent along with the last commit that reported, raises a Trello card for each silent repo and flag, and files the dated record in Google Drive.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Codecov find repos that stopped uploading
2 Trello raise a card per silent repo
3 Google Drive file the dated record
In short

How do I know when a repo stops uploading coverage to Codecov?

WebRun checks Codecov every morning for repositories that have stopped uploading coverage, naming the last commit and branch that did report. It raises a Trello card per silent repo or flag and files a dated record in Google Drive, so a green dashboard is never just missing data.

  • A broken upload step is caught the next morning, not the next quarter
  • Each card names the last commit that reported, so the break is traceable
  • Single silent flags are found inside repos that otherwise look healthy

Built for engineering managers · build owners · platform teams · QA leads

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.codecov.io/login in a real browser with your saved login - no setup, no API keys.

  2. 1
    Codecov - find repos that stopped uploading
    codecov.io
    WebRun in Codecov: find repos that stopped uploading
    WebRun opens Codecov to find repos that stopped uploading.
    • Open Codecov and list every repository in your organisation with its most recent upload
    • Flag any repository whose last coverage upload is older than the silence window you set
    • Record the last commit and branch that did report, with its date
    • Check the flags inside each active repository and note any flag that has stopped reporting while others continue

    Done when Every repository has a last upload date and a reporting or silent verdict, flag by flag.

  3. 2
    Trello - raise a card per silent repo
    trello.com
    WebRun in Trello: raise a card per silent repo
    WebRun opens Trello to raise a card per silent repo.
    • Raise a card on your build board for each silent repository or flag
    • Put the repository, the branch, the last reporting commit, and the date it stopped in the card
    • Update the existing card instead of opening a new one when a repo has been silent for several days

    Done when Every silent repository has one live card naming the last commit that reported.

  4. 3
    Google Drive - file the dated record
    drive.google.com
    WebRun in Google Drive: file the dated record
    WebRun opens Google Drive to file the dated record.
    • Save a dated record to your engineering folder listing every repository and its last upload
    • Keep the format identical each day so the folder shows when reporting broke
    • Highlight repositories that changed state since yesterday

    Done when Today's coverage upload record is filed in Google Drive.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.codecov.io/login
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Silent repo report · Trello
OutputWhat each run produces - Every Codecov repository with its last coverage upload, plus the silent ones named with the last commit and branch that reported.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it change our CI or re-run a build?

No. WebRun only reads Codecov. It never edits a pipeline, retriggers a build, changes a repository setting, or comments on a pull request. Findings land in Trello and a Drive record for your team.

How does it decide a repo has gone silent?

It compares each repository's last coverage upload against the silence window you set, then names the last commit and branch that did report so the break can be traced.

Does it catch a single broken flag?

Yes. It checks flags inside active repositories too, so a repo that still uploads but has lost one flag is caught rather than passing as healthy.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.