Move the module path to git.z.gd/zzg/fathom #2

2026-09-19T20:31:29-07:00

zzg commented

2026-09-19 20:31:29 -07:00

The module was declared github.com/zzg/fathom, which is not where this repo lives and never has been. Nothing is published at that path, so go get github.com/zzg/fathom resolves to a 404 while every import path in the tree asserts otherwise.

git.z.gd is a real module path, not a cosmetic correction. Gitea serves the vanity-import meta tag:

$ curl -s 'https://git.z.gd/zzg/fathom?go-get=1' | grep go-import
<meta name="go-import" content="git.z.gd/zzg/fathom git https://git.z.gd/zzg/fathom.git">

and the repo answers unauthenticated over HTTPS (200), so go get git.z.gd/zzg/fathom resolves where the old path could not.

Scope

Mechanical: the module line plus 46 import paths across 23 files. No go.sum to churn — fathom has no third-party dependencies. Nothing outside .go files referenced the old path; the README already uses git clone https://git.z.gd/zzg/fathom.git.

Verification

gofmt -l . empty, go build ./... clean, go vet ./... clean, go test ./... green across all 8 packages, and the built binary still runs (fathom 0.1.0-dev).

Note for merge order

insights-attr-aliases (#1) is rebased on top of this branch, so merge this one first. That PR then applies cleanly and contains only its own behavioural change.

🤖 Generated with Claude Code

The module was declared `github.com/zzg/fathom`, which is not where this repo lives and never has been. Nothing is published at that path, so `go get github.com/zzg/fathom` resolves to a 404 while every import path in the tree asserts otherwise. `git.z.gd` is a real module path, not a cosmetic correction. Gitea serves the vanity-import meta tag: ```console $ curl -s 'https://git.z.gd/zzg/fathom?go-get=1' | grep go-import <meta name="go-import" content="git.z.gd/zzg/fathom git https://git.z.gd/zzg/fathom.git"> ``` and the repo answers unauthenticated over HTTPS (200), so `go get git.z.gd/zzg/fathom` resolves where the old path could not. ## Scope Mechanical: the `module` line plus 46 import paths across 23 files. No `go.sum` to churn — fathom has no third-party dependencies. Nothing outside `.go` files referenced the old path; the README already uses `git clone https://git.z.gd/zzg/fathom.git`. ## Verification `gofmt -l .` empty, `go build ./...` clean, `go vet ./...` clean, `go test ./...` green across all 8 packages, and the built binary still runs (`fathom 0.1.0-dev`). ## Note for merge order `insights-attr-aliases` (#1) is rebased on top of this branch, so **merge this one first**. That PR then applies cleanly and contains only its own behavioural change. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

zzg added 1 commit 2026-09-19 20:31:30 -07:00

Move the module path to git.z.gd/zzg/fathom 79fe343be5

The module was declared as github.com/zzg/fathom, which is not where
this repo lives and never has been. Nothing is published at that path,
so `go get github.com/zzg/fathom` resolves to a 404 while the import
paths in every file assert otherwise.

git.z.gd is a real module path rather than a cosmetic correction:
Gitea serves the go-import meta tag for it,

  <meta name="go-import" content="git.z.gd/zzg/fathom git https://git.z.gd/zzg/fathom.git">

and the repo answers unauthenticated over HTTPS, so `go get
git.z.gd/zzg/fathom` resolves where the old path could not.

Mechanical: the module line plus 46 import paths across 23 files. There
is no go.sum to churn, since fathom has no third-party dependencies.
go build, go vet, gofmt and the full test suite are clean under the new
path, and the built binary still runs.

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

zzg referenced this pull request

2026-09-19 20:32:11 -07:00

Read insight attributes as aliases, not as one emitter's vocabulary #1

zzg commented

2026-09-19 20:36:08 -07:00

Merged to main by fast-forward, so history stays linear and the commit SHA is preserved: 79fe343.

* 79fe343 Move the module path to git.z.gd/zzg/fathom   <- main
* 13b7ebf Fix the span-tree pane not scrolling on a long trace

No merge commit. #1 was already based on 79fe343, so it now sits directly on top of main and needs no rebase.

Closing manually — the commit is on main, but a fast-forward push does not auto-close the PR here.

Merged to `main` by fast-forward, so history stays linear and the commit SHA is preserved: `79fe343`. ``` * 79fe343 Move the module path to git.z.gd/zzg/fathom <- main * 13b7ebf Fix the span-tree pane not scrolling on a long trace ``` No merge commit. #1 was already based on `79fe343`, so it now sits directly on top of `main` and needs no rebase. Closing manually — the commit is on `main`, but a fast-forward push does not auto-close the PR here.

zzg closed this pull request

2026-09-19 20:36:08 -07:00

Pull request closed

Please reopen this pull request to perform a merge.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: zzg/fathom#2