mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-26 01:36:03 +03:00
[GH-ISSUE #163] .markdownlint format optional extension #1988
Labels
No labels
bug
enhancement
enhancement
enhancement
fixed in next
fixed in next
fixed in next
new rule
new rule
new rule
pull-request
question
refactoring
refactoring
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/markdownlint#1988
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @syntaqx on GitHub (Feb 3, 2019).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/163
It would be awesome if both
.markdownlint.yamland.markdownlint.ymlwere supported as file extensions. Because YAML recommends.yamlif both files exist, it's reasonable that this should be loaded and the other ignored.The main reasons for supporting this additional extension are:
.theirtool.yml. (.travis.yml,docker-compose.yml,heroku.yml,.golangci.ymlto name a few)Long story short, my repository has a bunch of these configuration files for the various tools I implement, and
.markdown.yamlis the only one using.yamlas an extension. It's triggering my punctilious organizational symmetry preferences, and I need your help.<3
@DavidAnson commented on GitHub (Feb 3, 2019):
This appears to be a duplicate of https://github.com/DavidAnson/vscode-markdownlint/issues/60 which I expect to get to soon.
@syntaqx commented on GitHub (Feb 3, 2019):
My apologies for the duplicate! Excited that others also would like the functionality though :) Would you like me to close this out and use the other ticket for tracking?
@DavidAnson commented on GitHub (Feb 3, 2019):
Yes, let’s!