Nico MASSART

> But if you refuse the PR, no problem, I can just remove mega-linter.yml in the workflow and just publish the README and fixes I perform, please let me know...

@cadeef What would be the downside of not publishing the Docker image on PRs? The token is only for pushing to the GH registry, isn't it? Only building the image...

I agree with both of you on this one: making sure image is ok in as soon as possible is the way to go. But only the build is necessary...

I confirm that we don't have path exclusion yet. Multiple options are possible: - add a feature to handle an ignore file like the .gitignore one but named .markdownlinkignore that...

Not for implementors: it will require to refactor the ignore system as it removes lines before the MD is parsed so the lines would be wrong.

Would you like to have an option to enable that behaviour, and keep the current behaviour as the default one? Behaviour would be : ``` for each link in the...

I'd like that as for me, the root `index.md` at least should not raise a warning as I don't need it in the nav...

@aprilmintacpineda any news form support on this?

FYI, as a workaround I use aws cli to get the api key form cloudfront once deployed: https://docs.aws.amazon.com/cli/latest/reference/apigateway/get-api-keys.html

Also the code block first line could contain more than one word if you use extensions like [fenced-codeblock](https://python-markdown.github.io/extensions/fenced_code_blocks/): ```markdown ```bash tab="Syntax" # this is my comment in bash syntax about...