-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specify Markdown Style #2
Comments
Good idea. This would be a great use case for using a Github Action to automatically run a linter like markdownlint on all PRs. I'll add a |
Oo i like the github action idea. I forgot that actions are now free for public repo! |
Yeah they're pretty sweet. I've set up a few on different projects and could help give some guidance and answers questions, but I haven't done Markdown linting (or actually any linting) with them before, so the specifics would take some research time that I don't have at the moment. |
If the goal is to be similar to an awesome list, they have a simple linter (source) |
I tried to implement it using markdownlint-cli2-action. My approach is on my forked project. However, it does not work. I tried to set the contribution rules as custom rules using JavaScript (see code, but it seems like code dependencies cannot be added dynamically to Github Actions(see issue). Any suggestion on what to do and how ? |
Since we are using markdown in the main readme, perhaps we should specify the markdown format/linter we want to use/recommend in order to enforce consistency? I think VSCode uses markdownlint by default.
The text was updated successfully, but these errors were encountered: