Skip to content

docs: anchor VT badge to #virustotal-scans section#17

Merged
carterscode merged 1 commit into
mainfrom
docs/vt-badge-anchor
May 8, 2026
Merged

docs: anchor VT badge to #virustotal-scans section#17
carterscode merged 1 commit into
mainfrom
docs/vt-badge-anchor

Conversation

@carterscode

Copy link
Copy Markdown
Owner

Summary

One-character behavior change: appends #virustotal-scans to the VT badge link. Click now scrolls directly to the scan URLs at the bottom of the release notes instead of landing at the top of the page.

The anchor is auto-created by GitHub from the ## VirusTotal scans header that release.yml appends to the body. Browsers preserve URL fragments through the /releases/latest → tag redirect, so the anchor works even though latest is a 302.

Caveat

Anchor only resolves if the most recent release actually has VT URLs in its notes. v0.1.35 was cut while ENABLE_VIRUSTOTAL was false — its release notes don't have the section. Until the next release runs with VT enabled, clicking the badge lands at the top of the release page (no worse than today). The next release that exercises the VT step will have the section, and the anchor will work.

Path-filter check

README.md isn't in release.yml's path filter — won't trigger a release.

release.yml appends per-release VT scan URLs under a '## VirusTotal
scans' header in the release notes. GitHub auto-creates the anchor
'#virustotal-scans' for that header. Adding the fragment to the
badge URL makes clicking the badge land directly on the scan list,
not at the top of the release page.

Browsers preserve URL fragments across the /releases/latest -> tag
redirect, so the anchor works even though 'latest' is a 302.
@carterscode carterscode merged commit e10cb40 into main May 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant