Skip to content

chore: move repository references to Twigpine/zero - #1105

Open
PierrunoYT wants to merge 1 commit into
Twigpine:mainfrom
PierrunoYT:chore/rename-repo-to-twigpine
Open

PierrunoYT wants to merge 1 commit into
Twigpine:mainfrom
PierrunoYT:chore/rename-repo-to-twigpine

Conversation

@PierrunoYT

Copy link
Copy Markdown
Contributor

What changed

Replaces Gitlawb/zero with Twigpine/zero in tracked files (Go module path and imports, install scripts, docs, workflows, packaging, action.yml defaults, mise entries).

Intentionally unchanged:

  • npm scope @gitlawb/zero (published package name)
  • LICENSE copyright and author: in action.yml
  • GitLawb OpenGateway provider identifiers and URLs
  • Historical CHANGELOG.md links
  • Gitlawb/homebrew-tap (separate repository)
  • Arbitrary Gitlawb/... fixture strings in internal/update and internal/cli tests

Why

The repository now lives at https://github.com/Twigpine/zero.

Verification

  • go build ./..., go vet ./..., git diff HEAD --check: clean
  • go test ./...: internal/update, npmwrapper, release, installtest, doctor pass. Failures remain in internal/agent, internal/config and internal/cli on my Windows machine. agent and config fail identically on unmodified upstream/main. I did not re-run cli on the base.
  • Not run: make fmt-check (no make on this machine; gofmt -l lists only internal/perfbench/testdata), zero-release build/smoke, make lint-static, make vulncheck.

Parent issue: none linked yet.

🤖 Generated with Claude Code

Update the Go module path, imports, install scripts, docs, workflows,
packaging and action defaults from Gitlawb/zero to Twigpine/zero. The npm
scope, LICENSE, action author and the OpenGateway provider are unchanged,
as are historical CHANGELOG links.

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

@Vasanthdev2004 Vasanthdev2004 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at 87df72d9. The replacement looks complete for repository references. What's left of gitlawb is the npm scope, the AIMLAPI partner name and two comments, one of which names the tap. The -X path in BuildLdflags moved too, and zero-release build and smoke stamp 0.9.0 here, so version stamping survived. go build, go vet and the update, release, installtest, npmwrapper and doctor tests pass on Windows.

I'd like it split, though, and the module path needs a decision from @kevincodex1:

  • The runtime defaults should go in on their own. DefaultRepository in internal/update, ZERO_REPO in both install scripts, the postinstall REPO, the Action's zero-repo and the install URLs in the README are what installs and zero update actually fetch from. Until they move, every one of them reaches the release through GitHub's redirect from the old name. That's a small PR that can land now.
  • The module path is a bigger change than it looks. 59 of the other 62 open PRs touch Go files, and once go.mod says Twigpine, any of them that adds an import or a new file needs the same rename before it compiles. When to do that is kevin's call.
  • go install github.com/Twigpine/zero/cmd/zero@latest in docs/INSTALL.md fails until a release is tagged with the new module path. I tried it: v0.9.0's go.mod declares github.com/Gitlawb/zero, so Go stops with "module declares its path as: github.com/Gitlawb/zero but was required as: github.com/Twigpine/zero". The docs should keep the old path until that release exists.
  • X-AIMLAPI-Integration-Repo changes too. That header is what AIMLAPI sees for attribution, so it needs kevin's yes rather than riding along with the rename.
  • Small: packaging/homebrew/zero.rb still names Gitlawb/homebrew-tap, which is now Twigpine/homebrew-tap.

It also needs a parent issue, as the description says. Requesting changes for the split and the install doc.

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.

2 participants