Skip to content

docs: use moq-go (not moq) as the interop-runner registration name#24

Merged
floatdrop merged 1 commit into
draft-18from
docs/interop-moq-go-naming
Jun 27, 2026
Merged

docs: use moq-go (not moq) as the interop-runner registration name#24
floatdrop merged 1 commit into
draft-18from
docs/interop-moq-go-naming

Conversation

@floatdrop

Copy link
Copy Markdown
Owner

The implementation is registered as moq-go in moq-interop-runner (images moq-go-relay / moq-go-client, GHCR ghcr.io/englishm/moq-interop-runner-moq-go-relay), but our docs invoked the runner with RELAY=moq / CLIENT=moq. This aligns all references.

Changed

  • STATUS.mdRELAY=moq / CLIENT=moqmoq-go
  • cmd/relay/README.md — "registered as moq" + runner invocations
  • cmd/interop-client/README.md — "the moq client role" + CLIENT=moq
  • interop/matrix.shRELAY=moq hint
  • MakefileCLIENT=moq hint

Docs-only; no behavior change.

🤖 Generated with Claude Code

The implementation is registered as `moq-go` in moq-interop-runner
(images moq-go-relay / moq-go-client), but our docs invoked the runner
with RELAY=moq / CLIENT=moq. Align all references.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@floatdrop floatdrop merged commit d458804 into draft-18 Jun 27, 2026
9 checks passed
@floatdrop floatdrop deleted the docs/interop-moq-go-naming branch June 29, 2026 12:32
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