-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Incompatibilities with some markdownlint rules #60
Comments
It is not incompatible - it just doesn't conform exactly to the default ruleset. It seems to work fine if you adjust the |
Changing the spacing, or some other unimportant aspect of the changelog format, is something we could do. But then it wouldn't be strictly compatible with the KeepAChangelog example changelog, and thus with other KeepAChangelog-related tooling. We could make it flexible, but then it would be less useful, because it can't apply the format for us automatically if it's flexible enough to accept both. |
Update: Keep a Changelog has changed its own changelog file to match |
This package produces
CHANGELOG.md
files that are incompatible withmarkdownlint
.The written changelog conforms exactly to the example from the Keep a Changelog website, but are its spacing conventions really relevant to the spec our our ability to parse a changelog?
I believe that the spacing is irrelevant to the Keep a Changelog spec, and we should make the output changelogs compatible with
markdownlint
at least in terms of spacing. There may even be an argument to integratemarkdownlint
into this tool, but that's a different question.Related: #50.
markdownlint
-compatibility appears to be largely equivalent with Prettier-compatibility.The text was updated successfully, but these errors were encountered: