Add markdown linter workflow#363
Merged
mcbarton merged 2 commits intocompiler-research:mainfrom Dec 3, 2024
Merged
Conversation
Collaborator
Author
|
I will edit a markdown file tomorrow to check the workflow works, see what the linter detects and fix what it detects so it passes. |
645a4e5 to
178ab2c
Compare
Collaborator
Author
|
@vgvassilev This PR is ready for review now that I have fixed the issues raised by the markdown linter. |
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
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 PR should add a markdown linter workflow. This workflow can be expanded in future to check other file formats.