Automated Codacy Repository Coverage Audits
Every Monday, WebRun opens Codacy, lists every repository in the organization with its quality gate, coverage reporting status, and analysed branches, texts the engineering lead the repositories that are unwired, and posts the full coverage audit to Microsoft Teams.
How do I check every repository is covered by code quality checks?
WebRun opens Codacy every Monday and lists every repository with its quality gate, analysed branches, and coverage reporting status. It texts your engineering lead the repositories that were never added or never wired up, and posts the full audit to Microsoft Teams, so the quality report reflects the whole codebase.
- Repositories with no gate or coverage surface every Monday
- Stale coverage pipelines are separated from missing ones
- The quality report reflects the whole codebase, not the wired part
Built for engineering leads · platform teams · DevOps engineers · CTOs
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 - check repository setup and coverage
codacy.com
WebRun opens Codacy to check repository setup and coverage. - Open Codacy and list every repository added to the organization
- Check whether each repository has a quality gate configured and which branches are analysed
- Check whether coverage reports are actually arriving, and when the last one landed
- Compare the list against the repositories you expect to be onboarded and flag any missing entirely
Done when Every repository is listed with its gate status, analysed branches, and last coverage report.
-
2
Twilio - text the lead the gaps
twilio.com
WebRun opens Twilio to text the lead the gaps. - Draft a short text listing repositories with no gate, no coverage, or no analysis at all
- Send it only to the engineering lead's own number
- Lead with the count of unwired repositories, then name the worst offenders
- Skip the text on weeks when everything is wired up
Done when The engineering lead has this week's gap list by text, or there were no gaps.
-
3
Microsoft Teams - post the full audit
microsoft.com
WebRun opens Microsoft Teams to post the full audit. - Post the full audit to your engineering channel: repositories covered, partly covered, and not covered
- Show the last coverage report date for each repository so stale pipelines are visible
- List repositories that were never added to Codacy separately
- Keep the audit internal to the engineering team
Done when The engineering channel has this week's repository coverage audit.
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 change any Codacy settings?
No. WebRun reads repository configuration and reports the gaps. It never adds a repository, edits a quality gate, or changes a code pattern, so your settings stay as your team left them.
How does it know a repository is missing?
It compares the repositories Codacy lists against the set you tell it should be onboarded, then reports anything on your list that Codacy has never analysed.
What counts as coverage not being wired up?
A repository added to Codacy that has never received a coverage report, or whose last report is older than the staleness window you set. Both appear separately in the audit.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.