Repository navigation
build: move the project to github.com/nerv-base/mytoken - #8
Merged
Merged
Conversation
MyToken!!!!! is now listed on the Awesome MyGo showcase; this adds its badge to the English and Chinese READMEs.
The repository lives under the nerv-base organisation now, but every pointer still said zzstar101/mytoken: the go.mod module path, the imports in 283 files, the Makefile PKG that feeds -X ldflags, and the badge, release and install.sh URLs in both READMEs. That made the new path unusable for the Go toolchain — `go install github.com/nerv-base/mytoken@latest` failed with "module declares its path as: github.com/zzstar101/mytoken but was required as: github.com/nerv-base/mytoken" — so the install command could not point at nerv-base until the module path moved with it. - go.mod: module github.com/nerv-base/mytoken - imports rewritten in 283 files (690 import lines); gofmt re-sorted the blocks whose order changed - Makefile: PKG := github.com/nerv-base/mytoken, verified by building with -X $(PKG)/internal/cli.Version=9.9.9 and reading it back from `mytoken version` - README.md / README.zh-CN.md: badges, Releases links and the install.sh / tarball URLs now use nerv-base/mytoken; the `go install` line documents the new path and says it needs the first tag cut after this change, since earlier tags still install through the old path that GitHub redirects Verified: gofmt -l clean, go build ./..., go vet ./..., GOOS=windows go vet ./..., go test ./... (65 packages ok). The zzstar101 name stays where it is a person rather than a path: LICENSE, THIRD_PARTY_NOTICES, mygo.json's maintainer and copyright, the README copyright lines, and the historical CHANGELOG link.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the move into the
nerv-baseorganisation: everything that still pointed atzzstar101/mytokennow points atnerv-base/mytoken, and the project gets its Awesome MyGo badge.Two commits, no hand-edited generated files, no behaviour change.
1.
readme: link the listing on Awesome MyGoOne line in each README's badge block:
The HTML form (not
[](…)) because Markdown is not parsed inside the surrounding raw<p align="center">block. Both URLs answer 200.2.
build: move the module path to github.com/nerv-base/mytokengo install github.com/nerv-base/mytoken@latestfailed before this:go.mod→module github.com/nerv-base/mytokengofmt -wre-sorted the blocks whose order changedMakefile→PKG := github.com/nerv-base/mytoken; checked by building with-X $(PKG)/internal/cli.Version=9.9.9and reading it back frommytoken versioninstall.shand tarball URLs, and thego installlineDeliberately unchanged — there
zzstar101is a person, not a path:LICENSE,THIRD_PARTY_NOTICES,mygo.json(copyright,maintainer), the README copyright lines, and the historicalCHANGELOG.mdrelease link for v0.1.3.Install command timing
go install github.com/nerv-base/mytoken@latestonly resolves once a tag carrying this go.mod is published, so the README says so and keeps the old path documented for older tags (GitHub redirects it). Re-tagging v0.5.7 or cutting v0.6.0 makes the new command work.Verification
go mod tidy -diffstill shows unrelated pre-existing go.sum staleness (github.com/egoist/mygo0.4.8/0.5.5 andgolang.org/x/sync0.23.0 leftovers); I left it out of this PR to keep the diff about the move only.