Skip to content

Verify Markdown Links workflow fails on schedule and workflow_dispatch events #27091

Closed

Description

Summary

The Verify Markdown Links workflow (.github/workflows/verify-markdown-links.yml) declares schedule (weekly Sunday cron) and workflow_dispatch triggers, but the underlying get-changed-files composite action only handles pull_request and push events. Every scheduled run fails immediately with:

Unsupported event type: schedule. Supported types: pull_request, push

This has been failing every Sunday since the workflow was introduced in PR #26219 (October 2025).

Steps to Reproduce

  1. Go to Actions → Verify Markdown Links → Run workflow
  2. Click "Run workflow" on any branch
  3. The run fails with: Unsupported event type: workflow_dispatch. Supported types: pull_request, push

Alternatively, wait for the weekly Sunday midnight UTC cron to fire — same error.

Expected Behavior

The workflow should enumerate all markdown files in the repository (since there is no diff to compare for cron/manual runs) and check their links for external link rot.

Actual Behavior

The get-changed-files action calls core.setFailed() because it has no code path for schedule or workflow_dispatch events — only pull_request and push.

Root Cause

.github/actions/infrastructure/get-changed-files/action.yml lines 75-77 — the else branch rejects any event type not in the supported list, and schedule/workflow_dispatch were never added.

Environment

  • GitHub Actions, actions/github-script@v7
  • Workflow: .github/workflows/verify-markdown-links.yml
  • Action: .github/actions/infrastructure/get-changed-files/action.yml

Activity

  1. microsoft-github-policy-service commented on Sep 20, 2026

    @microsoft-github-policy-service
    Contributor

    This issue has not had any activity in 6 months, if there is no further activity in 7 days, the issue will be closed automatically.

    Activity in this case refers only to comments on the issue. If the issue is closed and you are the author, you can re-open the issue using the button below. Please add more information to be considered during retriage. If you are not the author but the issue is impacting you after it has been closed, please submit a new issue with updated details and a link to this issue and the original.

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

    Resolution-No ActivityIssue has had no activity for 6 months or more

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions