mirror of
https://github.com/DavidAnson/markdownlint.git
synced 2026-04-25 01:05:55 +03:00
[GH-ISSUE #1555] FR: markdownlint config from external git repository #2554
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#2554
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 @volker-raschek on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/DavidAnson/markdownlint/issues/1555
Hello everyone,
I have several git repositories. There is a
markdownlint.yamlfile in each of them. My problem with the configuration file is that most of them are identical and only receive partial maintenance. In other words, only when someone is actively working on the repository.If the configuration file changes with regard to a newer markdownlint version, updated as dependency via dependabot or renovate, you would actually have to go through all projects and adapt them.
The opensource project renovate has a similar problem. They have solved the problem with configuration presets. I am therefore submitting a feature request here to integrate a similar workflow / configuration option to drastically reduce the maintenance of configuration files.
For example:
Volker
@DavidAnson commented on GitHub (Mar 31, 2025):
The
extendsproperty is already supported in.markdownlint.yamland can be used as you propose: https://github.com/DavidAnson/markdownlint?tab=readme-ov-file#optionsconfig@DavidAnson commented on GitHub (Apr 3, 2025):
Note that because
extendscan reference an installed npm package and npm can installdevDependenciesdirectly from git, the complete scenario described above is possible today.