-
-
Notifications
You must be signed in to change notification settings - Fork 244
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
How to make alive status codes 200/203 (markdown link check) expected behavior for MegaLinter? #1368
Comments
@bengeset96 if you define a If not defined, a default markdown-links-check config file is used ( see doc -> https://megalinter.github.io/beta/descriptors/markdown_markdown_link_check/ ) 203 seems to be a correct return code, so i'll update it to add 203 :) |
Awesome, thank you so much! Great 🥇 |
@bengeset96 you're welcome :) |
I can confirm it is now okay after changing docker image from megalinter:v5 to megalinter:beta. I have checked each console output from the markdown-link-check manually, and it is not giving me neither 200 or 203 anymore as before. Evidence from summary as well: |
Great, thanks for your feedback:) |
Hello project maintainers and contributors,
Using this awesome toolbox in ADO.
Previously when using markdown link check standalone without MegaLinter you could do something like this in a config.json file:
{ "aliveStatusCodes": [ 200, 203 ] }
Then in the YML:
How to enforce the same behavior when using MegaLinter?
Currently YML is like this example:
.mega-linter.yml in the root of repository is like this:
I see that it is possible to disable it in configuration file for MegaLint like.
DISABLE_LINTERS: MARKDOWN_MARKDOWN_LINK_CHECK
Then its off completely and that is not optimal.
I have tried to search documentation for this, but can't find it. Help me out and I would be really grateful =)
/Benjamin
The text was updated successfully, but these errors were encountered: