-
-
Notifications
You must be signed in to change notification settings - Fork 689
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
MD013 : Issue with MarkdownLint Configuration Ignoring Line Length Exceeding 80 Words #1136
Comments
The pre-commit configuration above is using "args" to say the YAML configuration file should be linted (and nothing else). You probably want to use the --config option and pass a glob like "**/*.md". Once that problem is fixed, the "ignores" override you have should no longer be necessary and the other configuration should be applied as expected. |
@DavidAnson I have try to add the below configuration. Which you have suggested but after that also It is not ignoring the file pre-commit-hook.yaml
markdownlint-cli2.yaml
Could you provide me the pre-commit hook config which I need to use in markdownlint-cli2 to ignore the line-length issue in table. Error:
|
This tool shows what it's doing at the beginning of its output. You can see that in your bottom snippet as something that looks like this: That tells us the syntax for "--config" was wrong because "=" should not be used there. The pre-commit syntax you show above looks reasonable to me, but I do not use pre-commit. In my own smoke test for pre-commit integration, I use this syntax and it seems to behave as expected: |
I've encountered while configuring MarkdownLint to ignore line length exceeding 80 words. Despite following the official documentation's guidance, the line length issue persists, and I seek assistance in resolving it.
Here's the current configuration I've set up:
I've integrated this configuration into the pre-commit setup as follows:
Despite these settings, MarkdownLint continues to flag lines exceeding 80 characters, contrary to my intent to ignore this rule. I'm uncertain where the misconfiguration lies and would appreciate any guidance or adjustments you could provide to resolve this issue effectively.
The text was updated successfully, but these errors were encountered: