You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will help us ensure consistency and quality in the various content sections of the web site.
Some of the common options will likely need to be changed: in-line HTML is needed, and I'm not sure what the work-around for "code blocks must have a language" (used for displaying terminal output) should be.
As part of this change, we'll need a serious linting pass on old content so then we can keep CI green.
The text was updated successfully, but these errors were encountered:
- Fixes#207
# Status
- [x] Split the PR
- [x] Merge #272 (do first to reduce dumb merge conflicts).
- [x] Fix all mdlint violations
- [x] Update CI to target `master` rather than `main` (or fix the branch name per #140 )
- [x] Add local rules to ignore the same lints to improve contributor experience. I followed [these instructions](https://github.com/DavidAnson/vscode-markdownlint#configure); simply renaming the version in the .github folder didn't resolve the problem for me.
This will help us ensure consistency and quality in the various content sections of the web site.
Some of the common options will likely need to be changed: in-line HTML is needed, and I'm not sure what the work-around for "code blocks must have a language" (used for displaying terminal output) should be.
As part of this change, we'll need a serious linting pass on old content so then we can keep CI green.
The text was updated successfully, but these errors were encountered: