fix: super-linter use v4.8.1, issue with latest #10108
Merged
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
zak-pawel
approved these changes
Nov 15, 2021
zak-pawel
added
the
ready for final review
reimda
approved these changes
Nov 15, 2021
3 tasks
powersj
pushed a commit
that referenced
this pull request
Nov 17, 2021
(cherry picked from commit c1263fb)
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.
The markdown linter is failing due to an issue with the latest version (v4.8.3), in the meantime updating the linter configuration to use an older version known to still work (v4.8.1).
Relevant issue: https://github.com/github/super-linter/issues/2128