Adopt credential safe CI and retire replaced source gitlinks
ci / docker-checkout-hostgateway (pull_request) Successful in 1s
ci / vet-and-test (pull_request) Successful in 7s

Why:
Make independent version consumption work from ordinary clones while retaining historical commits and existing branch workspaces.

Evidence:
SELF Dev task receipts record 24 CI boundary cases, all workflow syntax checks, readonly private-source prefetch in clean exports, provider tests and package installation without acquisition scripts. Platform CI remains pending.

Impact:
Remove only replaced index links, preserve old physical checkouts, and update dependency guidance. Library consumers retain their immutable versions until an explicit dependency update.

Refs:
Agent-System-Dev feature/dependency-workspace; approved versioned-dependency r1, U3-U7 and R15.
This commit is contained in:
2026-10-13 17:11:42 +00:00
parent 28d2d50743
commit f55c6b11b6
6 changed files with 504 additions and 25 deletions
+6 -10
View File
@@ -20,20 +20,16 @@
| 逻辑 ID | 路径 | 角色 |
|---|---|---|
| development-guidelines | `deps/development-guidelines` | development-only |
| development-guidelines | Dev `.workspace/Development-Guidelines`(源码锁固定) | development-only |
本库没有 Go 模块依赖。被消费时由父仓以 submodule 固定提交,例如 `deps/error-code-system`,并在父仓 `go.mod` 写:
```
require error-code-system v0.0.0
replace error-code-system => ./deps/error-code-system
```
主库只依赖标准库。消费方通过 `go get git-ssh.u1680832.nyat.app/weichen/Error-Code-System.git@<已审核提交>`
生成真实提交版本,go.mod/go.sum 是消费权威,正式测试关闭本地 Go 覆盖。
私有传输由 Dev 固定入口配置;旧提交保留自己的历史依赖方式。
克隆:
```bash
git clone --recurse-submodules ssh://git@git-ssh.u1680832.nyat.app:31411/weichen/Error-Code-System.git
git clone ssh://git@git-ssh.u1680832.nyat.app:31411/weichen/Error-Code-System.git
```
## 验证命令
@@ -57,5 +53,5 @@ WRITE_CATALOG=1 go test ./domains -run TestWriteCatalog -count=1
|---|---|---|---|---|
| 本地查询服务 | `GET /v1/codes` | 无远程写入 API;码表变更走本仓提交 | 无数据库,码在进程内注册表 | 重启进程 |
共享项及 ACL:无。部署、迁移、发布的审批依据与负责角色:合并进 `main` 由仓库所有者批准。消费方升级必须单独提交父仓 gitlink。
共享项及 ACL:无。部署、迁移、发布的审批依据与负责角色:合并进 `main` 由仓库所有者批准。消费方升级通过独立依赖 PR 采用版本。
实际制品/配置/schema 的查询方法:`./bin/errcode export` 或 `GET /v1/export`,以当前进程加载的注册表为准。