Lint markdown files during github actions CI#6068
Merged
microstudi merged 4 commits intodevelopfrom May 22, 2020
Merged
Conversation
mrcasals
previously approved these changes
May 4, 2020
Do it because CI is not able to find the executable.
jesusdb
approved these changes
May 12, 2020
Leusev
approved these changes
May 14, 2020
Contributor
Leusev
left a comment
There was a problem hiding this comment.
Looks good for me @tramuntanal
microstudi
approved these changes
May 22, 2020
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
🎩 What? Why?
Due to many changelog entries with markdown format misspellings we're re-enabling markdown linting. It was lost during migration to GitHub actions.
📌 Related Issues
📋 Subtasks
CHANGELOGentry📷 Screenshots (optional)