Issue #89: Fix markdown check not working properly #111
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…for markdown lint
rngadam
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request provides hotfix for the markdown lint workflow that wasnt working at all. The default configuration of the GH action only checks for markdown files at root directory. The hotfix enables validation recursively in all folders.
Also :
add config file to disable line length on headers, code blocks and tables
Resolve markdown violations that were not detected before hotfix
disable autofix
Update yaml lint workflow to reflect solution to keep standard (for optional config file applying to workflow)
enable a config file path parameter for both dead links action and markdown lint action.
Repositories that will need to be updated after this merge since they use custom config files: