| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix: repair module import clobbered by URL unification; move recovery contract to the guard script The URL unification commit rewrote every gitcode.com/gitcode-cli/cli occurrence in version.go — including the module import path, which is an identifier, not a URL. The broken build escaped that commit's verification because the scoop json.tool check (which fails on the manifest's legal # comments) short-circuited the && chain before go test ran. Restore the import; the module path stays gitcode.com/gitcode-cli/cli everywhere. The release-workflow contract test asserted the backslide refusal string lived inline in release.yml; the guard moved to scripts/npm-dist-tag-guard.mjs (locked by its own unit tests), so the contract now requires the workflow to invoke the script on both the main publish path and recovery. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
chore: unify repository URLs to atomgit-cli/cli The same binary advertised two homes: gc version printed gitcode.com/gitcode-cli/cli while the goreleaser brew homepage and release footer use gitcode.com/atomgit-cli/cli — and the latter is the actual origin remote. Unify every repository URL to atomgit-cli/cli: version.go (text and --json url field) with its three test assertions, the RELEASE.md download URLs, the scoop manifest, the CONTRIBUTING clone command, and AGENTS.md (repo references in CI description, actions examples, and the self-testing rule; the GitHub mirror org was stale too). The Go module path (gitcode.com/gitcode-cli/cli) and the npm package coordinate (@gitcode-cli/cli) are identifiers, not URLs, and stay untouched. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 |