vscode: associate dotfiles to stop markdownlint false positives - #2
Merged
Conversation
3 tasks
The IDE's markdownlint extension flags dotfiles whose first line happens to start with '#' (gitignore/properties comments) or '---' (YAML start) as malformed markdown. None of those are markdown; the fix is a one- line files.associations entry per dotfile that's affected in this repo. Pure IDE config change — zero effect on CI, build, or runtime. Matches the pattern landed in jellyrock/docs#1.
cewert
force-pushed
the
vscode/dotfile-associations
branch
from
May 21, 2026 17:02
48f1e39 to
e2af778
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
VSCode's markdownlint extension flags dotfiles whose first line happens to start with
#(gitignore/properties comment) or---(YAML doc start) as malformed markdown — spurious lint warnings in the IDE on files that aren't markdown.Fix:
files.associationsentries in.vscode/settings.jsonso VSCode applies the right language mode and the markdownlint extension stays out of these files.Pure IDE config — zero effect on CI, build, or runtime.
Mirrors the same pattern landed in
jellyrock/docs#1.Part of
Org-wide IDE hygiene followup to the Renovate consolidation. One PR per repo so it's reviewable independently.
Test plan