Skip to content

build: fix vcbuild lint skipping lint-md-build - #66467

Open
vedchaudhari wants to merge 1 commit into
nodejs:mainfrom
vedchaudhari:fix-vcbuild-lint-md
Open

vedchaudhari wants to merge 1 commit into
nodejs:mainfrom
vedchaudhari:fix-vcbuild-lint-md

Conversation

@vedchaudhari

Copy link
Copy Markdown

When vcbuild lint was run on Windows from a fresh git clone, it failed with Linting is not available through the source tarball. The Markdown linter wasn't installed because the :lint-js-fix path skipped lint-md-build.

This PR fixes the issue by changing the goto from lint-md to lint-md-build. The other path from :lint-js-fix already goes to lint-md-build. Similar to #61318.

I deleted tools\lint-md\node_modules and confirmed that vcbuild lint, vcbuild lint-js, and vcbuild lint-md all run successfully. There are no automated tests for vcbuild.bat, so I tested the fix manually.

Refs: #61318

Assisted-by: Claude Code (Claude Opus 5.5)

Jump to lint-md-build so vcbuild lint installs the Markdown linter.

Assisted-by: Claude Code
Signed-off-by: vedchaudhari <vedc2853@gmail.com>
@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to Node.js builds or CI infrastructure. needs-ci PRs that need a full CI run. windows Issues and PRs related to the Windows platform. labels Oct 2, 2026
@github-actions

github-actions Bot commented Oct 2, 2026

Copy link
Copy Markdown
Contributor

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

@aduh95 aduh95 added author ready PRs with CI started, the required approvals, and no outstanding review comments. request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. labels Oct 2, 2026
@github-actions github-actions Bot removed the request-ci Add this label to start a Jenkins CI on a PR. Only starts once the PR has an approving review. label Oct 2, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

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

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. build Issues and PRs related to Node.js builds or CI infrastructure. needs-ci PRs that need a full CI run. windows Issues and PRs related to the Windows platform.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants