Skip to content

Scheduled repository coverage check is failing on main #556

Description

@github-actions

The 🧭 Repository coverage check run below did not pass on main.

Read the failing step first. A failure at 🔑 Get GitHub App Token means the App credential needs attention. An UNDECLARED line names a live repository that deploy/ does not declare: adopt it in deploy/ (Observe-first), never by changing the live repository. A STALE-EXEMPTION line names an exemption in scripts/check-repository-coverage.sh to remove, and an UNSEEN line means the listing could not see the whole org. This issue is updated by every failing run and closed by the next passing one.

Activity

  1. self-assigned this
    on Oct 9, 2026
  2. added 2 commits that reference this issue on Oct 9, 2026
  3. devantler commented on Oct 9, 2026

    @devantler
    Contributor

    🤖 Generated by the Agentic Engineer

    The separate default-branch governance audit also fails: its repository and admin-team coverage step reports two policy findings across 26 active repositories. This independently corroborates the coverage gap tracked here.

    The declaration repair is already in #560 at e2529d2e56a0b97211ae881afa11cc2707610c0f, parked on the compiler prerequisite #559/#558. Keep acceptance open until the declarations are adopted and both the authenticated repository coverage check and governance audit pass on reviewed main.

  4. devantler commented on Oct 9, 2026

    @devantler
    Contributor

    🤖 Generated by the Agentic Engineer

    The compiler prerequisite has now been delivered: #558 merged at 63c59062489edbee907d2a4d5d06f01c57b7d58c, which is the current default-branch head, and #559 is closed.

    At the final source head a635c5d9224ec6998b6e9402f17a164da3dc58d4, the catalogue CI run succeeded. All five previously failing Go MegaLinter fixture jobs completed their actual lint action successfully; the separate production-interface fixture was skipped and is not counted. The complete check-run read returned 280 of 280 entries, with no pending or non-green result.

    Coverage repair #560 remains at e2529d2e56a0b97211ae881afa11cc2707610c0f, before that compiler merge. Its next delivery step is to integrate the current reviewed default branch, validate that new head, and complete substantive review before merge. Keep this acceptance issue open until the declarations are adopted and both the authenticated repository coverage check and governance audit pass on reviewed main.

  5. github-actions commented on Oct 9, 2026

    @github-actions
    Author

    ✅ https://github.com/devantler-tech/.github/actions/runs/37919594032 passed on main, so the repository coverage check is green again. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions