Skip to content

[workflow-patrol] Workflow drift detected: missing trigger callers for 10 workflow_call workflows #398

Closed as not planned

Description

@github-actions

Findings

1. Ten workflow_call workflow sources have no matching dogfood trigger workflow

Why this is drift

  • In .github/workflows/gh-aw-*.md, all 45 sources use on.workflow_call.
  • 35/45 (77.8%) have a matching .github/workflows/trigger-(name).yml caller, so this exceeds the 75% threshold.
  • The outliers still have consumer examples (gh-agent-workflows/(name)/example.yml) and README entries, which makes the missing trigger callers look like structural drift rather than intentional internal-only design.

Workflows missing trigger callers

  • .github/workflows/gh-aw-docs-patrol-external.md
  • .github/workflows/gh-aw-flaky-test-investigator.md
  • .github/workflows/gh-aw-issue-fixer.md
  • .github/workflows/gh-aw-mention-in-issue-no-sandbox.md
  • .github/workflows/gh-aw-mention-in-pr-no-sandbox.md
  • .github/workflows/gh-aw-newbie-contributor-patrol-external.md
  • .github/workflows/gh-aw-performance-profiler.md
  • .github/workflows/gh-aw-release-update.md
  • .github/workflows/gh-aw-scheduled-audit.md
  • .github/workflows/gh-aw-scheduled-fix.md

Majority pattern examples (trigger present)

  • .github/workflows/trigger-duplicate-issue-detector.yml:16 uses ./.github/workflows/gh-aw-duplicate-issue-detector.lock.yml
  • .github/workflows/trigger-pr-review.yml exists and follows the same trigger-(name).yml convention
  • .github/workflows/trigger-agent-suggestions.yml exists and follows the same convention

Not already tracked

Suggested Actions

  • Add trigger-(name).yml callers for each of the 10 workflows above (or explicitly document exempt workflows if intentional).
  • Regenerate any generated workflow artifacts (dogfood/compiled outputs) using the repository’s normal compile flow.
  • Add a guard/check that verifies every public gh-aw-*.md workflow_call source has a corresponding trigger-*.yml file.

Generated by Internal: Workflow Patrol

  • expires on Mar 3, 2026, 3:09 PM UTC

Activity

  1. github-actions commented on Mar 3, 2026

    @github-actions
    ContributorAuthor

    This issue was automatically closed because it expired on 2026-03-03T15:09:30.433Z.

    Closed by Workflow

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions