Skip to content

ci: add markdownlint step to lint workflow - #89

Open
adewolescott wants to merge 1 commit into
Flamki:masterfrom
adewolescott:ci/markdownlint-step
Open

ci: add markdownlint step to lint workflow#89
adewolescott wants to merge 1 commit into
Flamki:masterfrom
adewolescott:ci/markdownlint-step

Conversation

@adewolescott

@adewolescott adewolescott commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Adds the markdownlint CI step (npm run lint:md) to the lint workflow, gating docs PRs on MD040 fence-language and formatting rules.

⚠️ Merge after #88 — this step depends on the markdownlint tooling (config + lint:md script) that lands in #88. Merging this first would break CI.

Add a Check Markdown lint step (npm run lint:md) to lint.yml after the
Prettier check, gating docs PRs on MD040 fence-language and formatting
rules.

Depends on the markdownlint-cli2 tooling (config, scripts, lint-staged
entries) landing first in Flamki#88. Kept as a separate PR because
workflow-file changes require workflow-scoped credentials.
@vercel

vercel Bot commented Jul 31, 2026

Copy link
Copy Markdown

@adewolescott is attempting to deploy a commit to the flamki's projects Team on Vercel.

A member of the Team first needs to authorize it.

@coderabbitai

coderabbitai Bot commented Jul 31, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@adewolescott, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 36 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 35c143cb-3c99-431d-9d3d-fc90c0eef653

📥 Commits

Reviewing files that changed from the base of the PR and between 3ba57ff and a31bb5c.

📒 Files selected for processing (1)
  • .github/workflows/lint.yml

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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.

1 participant