Skip to content

Add a Markdown lint job - #91

Merged
sehkone merged 1 commit into
mainfrom
sehkone/issue-90
Aug 4, 2026
Merged

Add a Markdown lint job#91
sehkone merged 1 commit into
mainfrom
sehkone/issue-90

Conversation

@sehkone

@sehkone sehkone commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Closes #90.

What was wrong

Nothing checked the Markdown in this repository. AGENTS.md and CLAUDE.md were unlinted, and every sibling repository in the organization — aicers/roxyd, aicers/agentcoop, aicers/bootroot, aicers/crusher, aicers/giganto, the review-* repositories — lints its own.

The change

A standalone markdown job (display name Markdown) with a recursive glob, matching the shape aicers/roxyd and aicers/agentcoop use.

Standalone rather than a step inside check, for two reasons: a clippy failure should not hide the Markdown result, and the lint should survive if the expensive jobs are ever put behind a path filter — a docs-only change is exactly the change that needs it.

No .markdownlint-cli2.yaml is added. Stock defaults pass as-is; a config can be added later if a rule proves too strict, rather than pre-emptively.

Verification

  • markdownlint-cli2@0.23.2 — the version @v24 pins — run recursively against main locally reports 0 issues across both files with stock defaults.
  • actionlint (with shellcheck) is clean.
  • main has no branch protection, so no required-check change is needed.

Relationship to the other open pull request

There is a separate pull request in this repository scoping the CI triggers. The two touch different parts of ci.yml and were tested to merge cleanly in either order (git merge-tree, no conflict).

Out of scope

  • Adding a markdownlint config file.
  • CI triggers and path filtering.

Nothing checked the Markdown here. `AGENTS.md` and `CLAUDE.md` were
unlinted, and every sibling repository in the organization lints its
own.
Standalone rather than a step inside `check`, for two reasons: a clippy
failure should not hide the Markdown result, and the lint should survive
if the expensive jobs are ever put behind a path filter -- a docs-only
change is exactly the change that needs it.
No config file is added. Stock defaults pass as-is, verified against
`main` with markdownlint-cli2 0.23.2, the version `@v24` pins: 0 issues
across both files. A config can be added later if a rule proves too
strict, rather than pre-emptively.

Closes #90
@sehkone
sehkone merged commit 274b146 into main Aug 4, 2026
12 checks passed
@sehkone
sehkone deleted the sehkone/issue-90 branch August 4, 2026 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a Markdown lint job

1 participant