Closed tchx84 closed 3 months ago
It seems we need a markdown linter of some sort to spot these issues earlier on pre-commit or pre-merge.
It seems we need a markdown linter of some sort to spot these issues earlier on pre-commit or pre-merge.
I haven't really used a MD linter before, but found this https://github.com/markdownlint/markdownlint
I've used https://github.com/igorshubovych/markdownlint-cli, and I don't remember why not markdownlint. But we can try them. Would you prefer add as pre-commit or github actions on push / pull_request events ?
I've used https://github.com/igorshubovych/markdownlint-cli, and I don't remember why not markdownlint. But we can try them. Would you prefer add as pre-commit or github actions on push / pull_request events ?
We don't include the markdown files in the git repo, so neither would work. But we can suggest that step in https://github.com/tchx84/Gameeky/pull/129
I've used https://github.com/igorshubovych/markdownlint-cli, and I don't remember why not markdownlint. But we can try them. Would you prefer add as pre-commit or github actions on push / pull_request events ?
We don't include the markdown files in the git repo, so neither would work. But we can suggest that step in #129
Regarding the tool, let's use whatever you're familiar with.
@rffontenelle FYI