-
Notifications
You must be signed in to change notification settings - Fork 87
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
Allow for 'warn only' behavior #177
Comments
There's a request to make error/warning configurable per-rule: DavidAnson/markdownlint#254 But for this scenario, could you just ignore the tool's exit code? |
I'm currently running this in a GitHub Actions workflow and still working on how I can get it to "ignore" the error code. So TBD there :) Update: using While per-rule would also be nice (many linters support this as I'm sure you know) an overall setting is also. For this situation I would hate to have to go thru and specify every single supported rule just to override with "warn". |
FYI that CLI2 has a a GitHub Action ready to go: https://github.com/DavidAnson/markdownlint-cli2-action Here’s how to ignore a failure: https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error |
ah thanks for the GH Action reference! |
Would be nice if
markdownlint-cli
just allowed for output of linting violations but did notexit 1
. This would effectively be "warn" instead of "error".The text was updated successfully, but these errors were encountered: