feat: implement issue #581 — Fleet coverage + secret-scan backfill: prerequisite for requiring them in code-quality (#575 follow-up)

DO
2h ago
+974-10

User description

Problem

Fleet coverage + secret-scan backfill: prerequisite for requiring them in code-quality (#575 follow-up)

From the issue: Make coverage and Secret scan (gitleaks) fleet-wide required checks in standards/rulesets/code-quality.json — safely, without bricking any repo.

Risk

Medium — changes GitHub Actions workflow behavior, which is exercised only post-merge; verify via the affected workflow runs.

Test plan

Tests added/updated: test/scripts/backfill-ci-quality-jobs/backfill-ci-quality-jobs.bats. Verification: bash scripts/dev-lead-lint.sh (shellcheck --severity=warning) ran pre-commit; the bats suite runs in CI.

Rollback

Revert this PR. No non-revertible side effects (no tags, migrations, or external state).

Monitoring

Watch the affected workflow run(s) in the Actions tab and this PR's Lint check for regressions.

Closes #581


CodeAnt-AI Description

Add secret-scanning and coverage checks to existing repositories without replacing their CI workflows.

What Changed

  • Opens a standards-sync pull request for each eligible repository that is missing either check, while keeping its existing build and test jobs.
  • Skips checks already provided by another workflow and adds the standard Gitleaks configuration when needed.
  • Previews changes and verifies the checks across the fleet before they can be made required; repositories without a CI workflow or with conflicting job names are reported for manual follow-up.

Impact

✅ Secret scanning in backfilled repositories
✅ Coverage checks in backfilled repositories
✅ Fewer repositories blocked by required checks before rollout is verified

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.