-
Notifications
You must be signed in to change notification settings - Fork 7
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
Disable Markdown linter #126
Comments
I'd prefer the markdown linter to stay active! Instead I'd prefer to make "master" a protected branch and prohibit direct commits to it. As soon as my PR #124 is merged we are back to green |
can we configure GH to use a properly configured codespace for editing that includes md linter? |
@karniv00l with Simon's comment in discord the from view logical consequence would be to 'make "master" a protected branch' . |
validateLink.js has an dependency on markdownlint for below use case: # Tests for linkValidator.js
## 1. test case prevented by markdownlint MD034/no-bare-urls
[T] (https://wikiXfome.tech/01-test.md)
## 2. test case prevented by markdownlint MD034/no-bare-urls
blah (https://wiki.fome.tech/01-test.md)
|
I see that some of the contributors use Github to edit content, don't have immediate feedback about enforced markdown style, or just don't care, so I would suggest disabling this workflow, and lower the entry barrier + have more green check marks in the CI
The text was updated successfully, but these errors were encountered: