Skip to content

fix(ci): run Markdown lint on workflow changes - #416

Draft
vmfunc wants to merge 1 commit into
mainfrom
fix/markdown-lint-workflow-trigger
Draft

vmfunc wants to merge 1 commit into
mainfrom
fix/markdown-lint-workflow-trigger

Conversation

@vmfunc

@vmfunc vmfunc commented Oct 23, 2026 •

Copy link
Copy Markdown
Owner

Workflow-only changes to .github/workflows/markdown-lint.yml currently skip the Markdown lint workflow because its pull request path filter only includes **/*.md. Add the workflow's own path so changes to its action or configuration exercise the Markdown lint job, while preserving the existing Markdown filter and all job settings.

This is independent of #415 and retains reviewdog/action-markdownlint@v0.30.0.

Validation:

  • actionlint 1.7.12, Ruby/Psych YAML parsing and structural comparison, eight before/after path-filter cases (root/nested Markdown, this workflow, unrelated paths), and git diff --check all pass.
  • The remote commit 51c6876d7cde7eb3ac3a1a0fa4a94c3c2efd8794 has the locally tested tree 802e15e55bca3c9ea70cfe98b3f42551e7581ce2.
  • This workflow-only PR triggered Markdown lint, which passed. Its log confirms execution of v0.30.0 on the PR merge ref. YAML lint also passed.

The successful Markdown lint job establishes action execution, not validation of #415's v0.31.5 action or a lint-clean repository. Its log shows existing Markdown findings, filter_mode=added, and fail_level=none.

@github-actions github-actions Bot added size/xs <10 lines changed ci changes to CI/workflow files labels Oct 23, 2026
@github-actions

Copy link
Copy Markdown

pr summary

1 files changed (+1 -0)

category files
ci/workflows 1

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

Labels

ci changes to CI/workflow files size/xs <10 lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant