Skip to content

fix(docs): add explicit favicon metadata - #7

Merged
JSONbored merged 1 commit into
mainfrom
codex/docs-favicon-polish
May 26, 2026
Merged

fix(docs): add explicit favicon metadata#7
JSONbored merged 1 commit into
mainfrom
codex/docs-favicon-polish

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • add explicit SVG favicon metadata to the VitePress docs head
  • update the root changelog for the docs polish fix

What changed

  • links /logo.svg as the docs favicon
  • keeps GitHub Pages as the only docs deployment path

Why

  • browser smoke found a /favicon.ico 404 after the version-widget deployment

Validation

  • npm run docs:build
  • npm run docs:smoke
  • npm run test:ci

@JSONbored
JSONbored merged commit 77023c3 into main May 26, 2026
1 check passed
@JSONbored
JSONbored deleted the codex/docs-favicon-polish branch May 26, 2026 15:57
@JSONbored JSONbored added the gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier. label Jun 10, 2026
bitfathers94 added a commit to bitfathers94/loopover that referenced this pull request Jul 26, 2026
…ntifier branch

IDENTIFIER_RE's third alternation group — a bare positive integer with no
`#`/`issue:` prefix — was reachable but unexercised: every identifier-bearing
case used `JSONbored#7` or `issue:12`. Add direct coverage asserting a bare trailing
integer resolves `identifier: issue:12` for both release and requeue, plus a
negative case proving a digit glued to a word (a `v2` version tag) is not
misread as an identifier and falls back to a repo-only target.

Closes JSONbored#8671
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:bug Gittensor-scored bug fix — scores a 0.05x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant