Skip to content

docs: point rind links at kixel-ai - #238

Draft
kixelated wants to merge 1 commit into
mainfrom
rind-kixel-ai
Draft

kixelated wants to merge 1 commit into
mainfrom
rind-kixel-ai

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Problem

rind moved from the moq-dev org to kixel-ai. The rind blog post, its charts, and the refresh tooling still link moq-dev/rind, which works only through GitHub's redirect.

Approach

Replace moq-dev/rind with kixel-ai/rind in link targets and link text: the chart's commit link builder, libraries.json and refresh.ts (ALGORITHMS.md link), tally.json's PR link, tally.tsx's link text, the blog post's two links, and tools/rind/README.md. The post's prose is otherwise unchanged.

refresh.ts reads a local rind checkout and calls no GitHub API, so nothing else fetches by the old name.

tally.json's scope keeps "whose task names moq-dev/rind": it describes how the tally selected sessions, by the name those tasks used at the time.

Impact

  • None: site content and tooling docs only.

Validation

  • git grep -n 'moq-dev/rind' lists only the scope line above.
  • just check (biome, tsc, quest check) passes.
  • bun astro build --mode live builds 40 pages; the built output links only kixel-ai/rind (post links, ALGORITHMS.md, PR 499, quest tree, and chart commit ccdda859), and each returns 200 from github.com without a redirect.

Alternatives

  • Leave the redirect in place: it breaks if a new repository ever takes the old name.

Follow-ups

None.

Models

Size: XS
Implementer: Claude Code, claude-opus-5-5, high effort

(Written by Claude Opus 5.5 with high effort)

🤖 Generated with Claude Code

rind and rind-patch moved from moq-dev to kixel-ai; link there directly
instead of relying on GitHub's redirect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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