Repository navigation
[BUG] Quarto markdown (.qmd) files aren't being recognized despite qmd in fileExtensions #2
Description
Describe the bug
I migrated from markdown-link-check and I want to check .qmd files. I added qmd to fileExtensions: in the .linkspector.yml, and I tried to point to a specific .qmd file with files:
It's hard to debug this since the action doesn't give stats about which files it reads (like the -s option when it runs locally).
To Reproduce
Steps to reproduce the behavior:
Add a .qmd (quarto markdown) file to a repo, then configure .linkspector.yml as follows:
files:
- ./monets.qmd
dirs:
- ./
fileExtensions:
- qmd
- md
useGitIgnore: falseI'm sure it's picking up the right config file.
I created a copy of a qmd file in my repo and renamed it with .md and it's being checked. Here's the output in an actual action:
Run umbrelladocs/action-linkspector@v1
Run actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444
1s
Run actions/setup-node@a0853c24544627f65ddf259abe73b1d18a591444
Found in cache @ /opt/hostedtoolcache/node/24.20.0/x64
(node:2234) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
Environment details
Set reviewdog version
0s
Cache reviewdog binary
1s
Run actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae
Cache hit for: reviewdog-Linux-X64-v0.21.0
Received 4393735 of 4393735 (100.0%), 11.6 MBs/sec
Cache Size: ~4 MB (4393735 B)
/usr/bin/tar -xf /home/runner/work/_temp/4468f015-5ade-4a1b-bdc4-07e09d00a1cf/cache.tzst -P -C /home/runner/work/fuhrmanator.github.io/fuhrmanator.github.io --use-compress-program unzstd
Cache restored successfully
Cache restored from key: reviewdog-Linux-X64-v0.21.0
Add cached reviewdog to PATH
0s
Run if [ -n "${INPUT_FAIL_LEVEL}" ]; then
0s
Run $GITHUB_ACTION_PATH/script.sh
34s
Run $GITHUB_ACTION_PATH/script.sh
🔗💀 Setting up Chrome Linux Sandbox
🔗💀 Installing linkspector ... https://github.com/UmbrellaDocs/linkspector
Running linkspector with reviewdog 🐶 ...
message:"Cannot reach https://www.linkedin.com/in/fuhrmanator/ Status: 999" location:{path:"index copy.md" range:{start:{line:12 column:13} end:{line:12 column:53}}} severity:ERROR source:{name:"linkspector" url:"https://github.com/UmbrellaDocs/linkspector"}
message:"Cannot reach https://profs.etsmtl.ca/cfuhrman/ Status: 404" location:{path:"index copy.md" range:{start:{line:26 column:100} end:{line:26 column:161}}} severity:ERROR source:{name:"linkspector" url:"https://github.com/UmbrellaDocs/linkspector"}
time=2026-09-13T21:58:50.336Z level=INFO msg="reviewdog: failed to post a review comment: POST https://api.github.com/repos/fuhrmanator/fuhrmanator.github.io/pulls/21/reviews: 403 Resource not accessible by integration []"
reviewdog: This GitHub Token doesn't have write permission of Review API [1],
so reviewdog will report results via logging command [2] and create annotations similar to
github-pr-check reporter as a fallback.
[1]: https://docs.github.com/en/actions/reference/events-that-trigger-workflows#pull_request_target
[2]: https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions
reviewdog: found at least one issue with severity greater than or equal to the given level: any
Error: Process completed with exit code 1.
There's an identical file index.qmd that is not being scanned, despite the fileExtensions:. Perhaps .qmd isn't recognized as .md (qmd link syntax is virtually identical).
Expected behavior
Quarto markdown should be recognized as markdown for the purposes of link checking.
It's not a MWE, but the repo and PR where I'm trying this is: fuhrmanator/fuhrmanator.github.io#21
Running it locally, I get seemingly inconsistent results. I redacted the output a bit for privacy.
It finds the specific file (monets.qmd) and finds the links inside (implying it's parsing .qmd files properly). With the same config, it's not finding the copy of index.md or index.qmd files, but perhaps that's a path issue under git bash with Windows (dirs: set to ./).
$ npx @umbrelladocs/linkspector check -c .linkspector.yml -j
npm notice run npx
npm notice run linkspector check -c .linkspector.yml -j
{
"source": {
"name": "linkspector",
"url": "https://github.com/UmbrellaDocs/linkspector"
},
"severity": "ERROR",
"diagnostics": [
{
"message": "Cannot reach https://[redacted] Status: 403",
"location": {
"path": "monets.qmd",
"range": {
"start": {
"line": 12,
"column": 3
},
"end": {
"line": 12,
"column": 75
}
}
},
"severity": "ERROR"
}
]
}
I've enabled the stats and QMD files are being checked. They have errors, but everything is green. I tried various combinations of fail_level (in the action) and it changes nothing.
This looks like a duplicate of #147.
Activity
fullsend-ai-triage commentedon Nov 13, 2026
🤖 Finished Triage · ✅ Success · Started 1:40 AM UTC · Completed 1:46 AM UTC
Commit:
4fe27f4· View workflow run →Runtime: pi · Model: google-vertex/gemini-3.8-flash → gemini-3.8-flash · Effort: high · Cost: $0.42
fullsend-ai-triage commentedon Nov 13, 2026
Thank you for reporting this issue. This report is being closed as not planned because Linkspector already supports Quarto Markdown (
.qmd) files when configured infileExtensions.How Linkspector processes
.qmdfilesWhen custom extensions are specified under
fileExtensionsin.linkspector.yml:.qmd) is matched by the file discovery logic and passed to the Markdown parser (extractMarkdownHyperlinks), which parses standard Markdown link syntax.-jand the statistics view, Linkspector successfully discovered the.qmdfile, extracted its links, and identified broken targets.Why GitHub Actions appeared to skip the file
The GitHub Action (
umbrelladocs/action-linkspector) runs Linkspector through reviewdog. By default:filter_modeis set toadded: reviewdog only posts annotations and evaluates failures for lines newly added in the pull request diff. Existing files or unchanged lines containing broken links will not be annotated or fail the build under this mode.fail_leveldefaults tonone: reviewdog will not fail the step on detected errors unlessfail_levelis explicitly configured (for example,fail_level: any).If you want the action to report errors across all files regardless of PR diff changes, configure
filter_mode: nofilter(orfilter_mode: file) andfail_level: anyin your workflow step:Because the reported behavior is due to reviewdog's diff filtering in the GitHub Action rather than Linkspector failing to recognize
.qmdfiles, this issue does not require changes in Linkspector.Labels: Remove the bug label and apply invalid since Linkspector already supports Quarto markdown files when configured in fileExtensions.