Allow to specify config file location?

We currently use markdownlint for both GitHub action workflows and contributors who choose to use VS Code. Our config files live in a non-standard location for use with workflows (.github/configs/.markdownlint.json) it would be really nice if VS Code users could point their workspace settings at that file for linting use while they’re working on things.

I know we could move the file to the root and still use it in the workflows, however, keeping the root of the project tiddy is also a worthy goal so we’d like an option to support both uses with only one file in a non-standard location. (It doesn’t seem practical to keep settings files for VS Code/Eclipse/IntelliJ/Atom/whatever all in the root of the repo to facilitate whatever editor and add-ons users may choose to use, however, if we could say "If you’re using VS Code, you can lint locally by pointing at .github/configs/.markdownlint.json, that seems great.)

This would also impact the project’s ability to facilitate markdownlint’s use for GitHub Codespaces.

[DavidAnson]

This was a bug on my part - per the associated commit, the “extends” file should be resolved relative to HOMEDIR only if it came from user configuration. In your scenario, user and workspace configuration with non-overlapping properties get merged and the old logic resolved relative to HOMEDIR if ANY value came from user configuration. This should work as expected in the next release of the extension.

[DavidAnson]

@TomerFi, can you try running markdownlint-cli2 from the root of that repo and say if it works or not? Maybe we can narrow this down.