-
-
Notifications
You must be signed in to change notification settings - Fork 281
markdownlint-cli → markdownlint-cli2
#1934
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The only markdownlint test that I see failing is this one: I haven't been able to find any logs indicating why it's failing and I haven't figured out how to run the tests locally to debug further. Any help here would be greatly appreciated. 🙂 |
|
Maybe you can start y what are the advatages og megalinter to use maskdownlint-cli2 instead of markdownlint ? :) |
I'm not sure I understand the question... If you're asking what the advantages of |
I think this is very valid feedback. I am inclined to give our CI pipeline some love if @nvuillam agrees. I am open to suggestions on where to begin. Otherwise, I will just try to keep the PRs small in order to solicit feedback. |
|
It looks like the test is adding markdownlint-cli2 markdownlint-cli2 /tmp/lint/.automation/test/markdown/markdown_bad_1.md /tmp/lint/.automation/test/markdown/markdown_bad_2.mdThis appears to be because of how the container works. More on that here. If we want to use the container, we'll need to use the I'm going to see if the build success without the container and go from there. |
|
I think using npm package could be ok :) (all npm packages are joined in a single install command so it won't impact badly the build time) |
megalinter/tests/test_megalinter/helpers/utilstest.py:604: in assert_file_has_been_updated
test_self.assertTrue(updated, f"{file_name} has been updated")
E AssertionError: False is not true : markdown_for_fixes_1.md has been updatedIf I run the following command locally on this branch, 17 files, including npx mega-linter-runner --path .automation/test/sample_project_fixes/ --fixAny ideas why it might behave differently in the test? |
|
We're planning and have already some work merged for v9, a major version. @nvuillam what is your opinion on what we accept as changes to users? |
|
This PR has been open for way too long |
|
@echoix v9 is the next version (no ETA yet as we need to implement the custom flavors), so we can add breaking changes as long as we document them :) |
|
This pull request has been automatically marked as stale because it has not had recent activity. If you think this pull request should stay open, please remove the |
|
This pull request has been automatically marked as stale because it has not had recent activity. If you think this pull request should stay open, please remove the |
| "version": "latest", | ||
| "enableNonRootDocker": "true", | ||
| "moby": "true" | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug: Unintended Docker Configurations in PR
This PR includes devcontainer configuration for Docker-in-Docker and Buildkit. These changes appear to be accidental commits, unrelated to the markdownlint migration that is the focus of this PR.
Additional Locations (1)
|
This pull request has been automatically marked as stale because it has not had recent activity. If you think this pull request should stay open, please remove the |
|
Should I continue keeping this PR up-to-date by resolving conflicts as they arise? |

Proposed Changes
Replace
markdownlint-cliwithmarkdownlint-cli2.Motivation: MegaLinter doesn't currently play nice with directory-specific markdownlint configuration files. Using
markdownlint-cli2in place ofmarkdownlint-cliwill fix this.Advantages:
The markdownlint VS Code extension is powered by
markdownlint-cli2, so everything should just work without special configuration when using the extension in conjunction with MegaLinter.Additional information: https://dlaa.me/blog/post/markdownlintcli2
Readiness Checklist
Author/Contributor
Reviewing Maintainer
breakingif this is a large fundamental changeautomation,bug,documentation,enhancement,infrastructure, orperformanceNote
Replace
markdownlint-cliwithmarkdownlint-cli2throughout the codebase, updating Dockerfiles, descriptors, schema defaults, docs, tests, and versions; also enhance devcontainer with Docker-in-Docker support.markdownlint-cliwithmarkdownlint-cli2across core and flavorDockerfiles andlinters/markdown_markdownlint/Dockerfile(install args and packages).megalintermarkdown descriptor: setcli_executabletomarkdownlint-cli2, changeconfig_file_namedefault toLINTER_DEFAULT, add--help/--versionargs, refresh examples and links.MARKDOWN_MARKDOWNLINT_CLI_EXECUTABLE,MARKDOWN_MARKDOWNLINT_CONFIG_FILE) and generated linter versions/help outputs.markdownlint-cli2, new version, commands, and configuration guidance; add CHANGELOG note.markdownlint-cli2specific exit behavior.devcontainer: add Docker-in-Docker feature, Docker VS Code extension, andDOCKER_BUILDKIT=1.Written by Cursor Bugbot for commit 0c9961a. This will update automatically on new commits. Configure here.