Skip to content

feat(docs): refresh Gittensor-aligned homepage - #8

Merged
JSONbored merged 1 commit into
mainfrom
codex/docs-gittensor-home-refresh
May 26, 2026
Merged

feat(docs): refresh Gittensor-aligned homepage#8
JSONbored merged 1 commit into
mainfrom
codex/docs-gittensor-home-refresh

Conversation

@JSONbored

Copy link
Copy Markdown
Owner

Summary

  • refresh the docs homepage with a Gittensor-aligned black/green signal layout
  • replace the logo-only hero with a static optimized Gittensor context image
  • reorganize docs navigation around start, workflows, API, and safety
  • tighten install, MCP, miner, maintainer, and GitHub App setup copy

What changed

  • added site/public/images/gittensor-home-signal.webp as the homepage ecosystem context image
  • rewrote the homepage around scoreability, lane fit, queue pressure, reviewability, and metadata-only MCP workflows
  • updated VitePress nav/sidebar grouping and site metadata
  • extended docs checks to require the Gittensor context image in source and built output

Why

  • the previous homepage hero used the internal logo as decoration and did not communicate the Gittensor context
  • docs were too flat and repetitive for miners, maintainers, and MCP users trying to understand where to start

Validation

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

Notes

  • no backend/API behavior changed
  • no MCP package files changed and no npm release is needed
  • no Playwright or frontend browser test dependency was added

@JSONbored
JSONbored merged commit 669cbca into main May 26, 2026
1 check passed
@JSONbored
JSONbored deleted the codex/docs-gittensor-home-refresh branch May 26, 2026 16:58
@JSONbored JSONbored added the gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier. label Jun 10, 2026
loopover-orb Bot pushed a commit that referenced this pull request Jul 14, 2026
…om maybePublishPrPublicSurface (#4607) (#5787)

`maybePublishPrPublicSurface` is 2,600+ lines, and #4607's stated cost is that "most cross-cutting
review-pipeline concerns live as unnamed inline blocks in one function rather than named,
independently-testable steps". This lifts one such block into a named step.

`derivePublicCommentMergeFacts` derives the five merge/disposition values the public PR comment
renders -- ciState, mergeStateLabel, mergeReadiness, heldForReview, neverClosed -- from the live CI
aggregate, the live merge-state refresh, the repo settings and the changed files. Its output IS
buildUnifiedCommentBody's input contract for those fields, so the seam is a real step rather than an
arbitrary cut. It is pure: the `incr()` metrics emit that sat in the middle of the block stays at the
call site, since it reads the gate conclusion the derivation never sees.

These flags exist so the COMMENT agrees with the ACTION the disposition planner takes -- heldForReview
for a guardrail-touching diff (#guarded-hold-comment), neverClosed for an owner/protected-automation
author (#8/#9). Until now they were only reachable by standing up a whole webhook delivery: the
renderer's own suite passes them in as hand-written literals, and the queue suites exercise them
transitively. They now have direct table tests, including the empty-changed-file-list fail-safe (an
unresolved file list HOLDS for review rather than claiming safe-to-merge), which had no test at all.

No behavior change: the 882 tests in the existing queue suites pass unchanged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gittensor:feature Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant