| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(review): cover list-form placeholders, de-link the security pointer - PLACEHOLDER_RE now also matches list-wrapped placeholders ("- （…）"), closing the mixed-draft bypass where every section but 证据 is filled and its placeholder line slipped through - flagged independently by three reviewers - the bug template's relative spec link resolves against the repo root in issue-form rendering contexts and would 404 (known platform pitfall); the plain repository path keeps the guidance without the broken link Refs #614 Co-Authored-By: Claude Code <noreply@anthropic.com> | 10 天前 | |
docs(release): include !588 in the installer section header per re-review note The section body cites the completion command-name env pinning fix from !588, so the header's citation set gains !588 for exact consistency, as specified by the independent re-review. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
docs(sig): address strict review findings for SIG governance 修复三角色严格评审的 1 blocker + 15 major： - B1: discussion 依赖降级——Phase 1 以带 sig/* label 的 issue 为讨论通道； §6.2 明确平台 repo 级分类能力未验证、启用条件与迁移路径；YAML discussion_category 标注为规划值 - M1: 新增 scope_labels 可选字段（YAML + §5.2 + §6.1）显式映射 scope/* label， 未映射不计入活跃度；评估主体与节奏（sig/governance lead 月度）写入 §3 - M2: 豁免条款闭环——豁免有效期=整改窗口、终态=全部 SIG 脱离、逾期后果 （连续 2 个评估周期未整改触发 degraded 评估）、maintainer 人数判定来源 - M3: §9 补失败判定标准与回退动作清单（收缩 / 撤销单个 SIG / 整体回退） - M4: lazy consensus 补最短公示 ≥ 72 小时 - M5: §3 增加 incubating→archived 试点撤销路径、degraded 量化（lead 缺位 ≥ 2 周对齐 §4.4） - M6: 标注义务封闭集合移除不入库的 .codex-tmp 草稿路径 - M7: source-of-truth-matrix 登记 SIG 元数据与 RFC 流程真相源行；docs-governance §2.2/§3 同步 - M8: RFC 流程规则移入 spec/workflows/rfc-workflow.md，docs/rfcs/README.md 退化为导航； shelved 登记矛盾修正（登记表仅 accepted） - M9: AGENTS.md §2.4 与常用任务入口、CLAUDE.md、docs/README.md、CONTRIBUTING.md、spec/README.md 同步 SIG/RFC 入口 - M10: §4.3 补 Signed-off-by-Agent / Co-Authored-By 与既有审计 trailer 的正交关系 - M11: 校验脚本提取管道容错，坏文件不再静默中断整个校验 - M12: labels 校验改行级精确匹配，防 sig/<name>-xx 词边界绕过 - M13: 豁免一致性判定收紧为"同一单人列表"，与 §4.2 语义对齐（修误报与漏报） - M14: .gitleaks.toml 变更撤出本 PR（与 SIG 主题无关，另行单独 PR） - M15: 脚本加可执行位；另补 nullglob、ERROR 消息文件前缀、kebab 正则统一、 scope_labels 格式与跨文件查重校验、Makefile SIGS_DIR 透传 - 附带：RFC 模板补回滚策略节；§6.3 状态机改引 issue/pr-workflow.md； 试点周期对齐 4 周（第 2 周中期检查点）；label deprecated 操作方式明确； propose 不入 status 枚举的说明 验证：validate-sig-yamls.sh 正向 3 文件通过；负面测试矩阵 8 组全过 （多文件不中断、sig/api-v2 绕过、2 人重叠误报/漏报、scope_labels 非法条目、 跨文件重复映射、空目录等）；无 Go 代码变更，CI lint/test/build 不受影响。 | 1 个月前 | |
refactor: remove deprecated in-repo skills Refs #487 | 3 个月前 | |
docs(release): add v0.15.0 release notes and sync version metadata Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
fix(review): close placeholder bypass, anchor templates in workflow spec - section_content now treats whole-line full-width parentheticals as placeholders, so a template submitted as-is fails record mode exactly like the ten list-style kinds do; the convention is documented in the template itself (code review, empirically demonstrated bypass) - pre-draft checklist item 3 now also checks merged PRs / origin/main / recent releases, so fixed-but-unreleased bugs do not get duplicate issues (code review) - issue-workflow.md section 1 gains the template pointer line: web UI uses .github/ISSUE_TEMPLATE (dual-platform, experiment-verified), AI drafting starts from issue-create.md with the validate command - otherwise the four-section structure is enforced by tooling but recorded nowhere in the rule source (docs review) - AI-TEMPLATES.md last-updated stamp refreshed Remote probe cleanup on infra-test/gctest1 verified against origin/main and backfilled in the issue; the record-mode coverage gap is registered as a follow-up. Refs #614 Co-Authored-By: Claude Code <noreply@anthropic.com> | 10 天前 | |
test(review): pin guidance copy strings and align status doc granularity - envtoken table rows now assert the new copy (fresh-terminal verify, fallback hint, Windows irreversible/echo notes) so wording regressions are caught, per the docs review handoff note - status sections in both docs mention plan A verification runs in a fresh terminal, matching the login section granularity Refs #613 Co-Authored-By: Claude Code <noreply@anthropic.com> | 17 天前 | |
fix(review): pin success-state JSON and tighten always-present wording - add the success-path --json test (token_valid:true plus username, token_source, git_protocol), closing the three-state coverage of the always-serialized state booleans the test review flagged - docs/COMMANDS.md: the failure sentence now states both fields always serialize, per the docs review suggestion, so agent consumers know they can skip field-presence branching Refs #624 Co-Authored-By: Claude Code <noreply@anthropic.com> | 16 天前 | |
fix(review): address multi-role review findings for the 609 batch Four independent reviewers (code/security/test/docs) over the 6-commit batch: one P1, five P2s, and a set of P3s — all fixed here. P1 (code review, reproduced end-to-end): the shadow-skip broke the PRIMARY install path. npx/npm exec prepends the package's own npx-cache node_modules/.bin to PATH, so firstProviderOnPath resolved the package's own shims and every completion was skipped with a misleading warning — on a clean machine too. A provider now counts as self when it resolves into the same package tree that is running the installer (providerIsRunningPackage, realpath against the running package root); a different persistent install of our coordinate still shadows. The npx shape is reproduced in a sandbox fixture: 6/6 completions install, zero skips or warnings. Docs P2s: the PowerShell completion example wrote to $PROFILE.Completions, a nonexistent property — the redirect drops the script silently; now appends to $PROFILE. The zsh notice pointed at a README section that does not exist (both pointers now name the Uninstall section). spec and .devcontainer still taught the deleted make release-snapshot; AGENTS.md still called 'make release' the official publish after it became --skip=publish. AI-GUIDE and INTRODUCTION carried half-migrated repository slugs (clone commands and -R demo targets that hit the retired coordinate); dev-facing test rules and links unified too. Code P3s: BASH_COMPLETION_USER_DIR now requires absolute entries like the XDG vars (a relative value produced a CWD-relative write target); the upload precheck also refuses batch-internal duplicate basenames; --clobber against a directory says so instead of a raw is-a-directory error; the main npm job's post-publish verification loop normalizes failed lookups into retries like every other dist-tag check. Test P3s: the Go PATHEXT helper gains the table test mirroring its JS twin (the parity this batch is about had no Go-side pin); the mutually-exclusive-flags test asserts the cobra flag-group error text (a bare err != nil stayed green if the check were dropped); the workflow contract requires BOTH dist-tag-guard invocations (strings.Count == 2); the doctor human-output test pins the header order; upload gains the wrapped not-found (exit 3) and directory/batch-duplicate tests; providerIsRunningPackage and the relative BCUD entries get unit tests. Recorded without changes: api-doc/ is a separate repository (its slug stays), sparse-checkout for the npm job and the pre-existing dual download-artifact pin are noted for later, shadow run-level positive coverage rides the sandbox fixture above. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
docs: 飞书/Lark 通知首次使用指南 (LARK.md) Co-authored-by: aflyingto<wupengfei10@huawei.com> | 3 个月前 | |
fix(review): pin CI triggers and preflight tests in contracts, sync residual docs Review fixes (three reviewers converged on the contract gap): - ci workflow contract: workflowDocument now parses the on block and validateTriggers pins pull_request and push both covering main for BOTH workflow files (new mirror parity test - the GitHub side had zero contract coverage); containment semantics so future release/* branches do not break the pin; three mutation negatives prove the validator catches a removed or retargeted trigger, the exact regression that would recreate the d1714f0 blind spot - release workflow contract: preflight must run go test before the tag is created, pinning the release-time unit test gate - docs: LOOP-GOAL-GUIDE mirror-trigger sentence was stale, ci-workflows toolchain table now lists the push trigger, .loop lesson 9 updated, and the run-list examples gain --branch main --event Push queries for the issue acceptance verification Refs #618 Co-Authored-By: Claude Code <noreply@anthropic.com> | 16 天前 | |
refactor: remove deprecated in-repo skills Refs #487 | 3 个月前 | |
docs(release): add v0.15.0 release notes and sync version metadata Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
docs(sig): address strict review findings for SIG governance 修复三角色严格评审的 1 blocker + 15 major： - B1: discussion 依赖降级——Phase 1 以带 sig/* label 的 issue 为讨论通道； §6.2 明确平台 repo 级分类能力未验证、启用条件与迁移路径；YAML discussion_category 标注为规划值 - M1: 新增 scope_labels 可选字段（YAML + §5.2 + §6.1）显式映射 scope/* label， 未映射不计入活跃度；评估主体与节奏（sig/governance lead 月度）写入 §3 - M2: 豁免条款闭环——豁免有效期=整改窗口、终态=全部 SIG 脱离、逾期后果 （连续 2 个评估周期未整改触发 degraded 评估）、maintainer 人数判定来源 - M3: §9 补失败判定标准与回退动作清单（收缩 / 撤销单个 SIG / 整体回退） - M4: lazy consensus 补最短公示 ≥ 72 小时 - M5: §3 增加 incubating→archived 试点撤销路径、degraded 量化（lead 缺位 ≥ 2 周对齐 §4.4） - M6: 标注义务封闭集合移除不入库的 .codex-tmp 草稿路径 - M7: source-of-truth-matrix 登记 SIG 元数据与 RFC 流程真相源行；docs-governance §2.2/§3 同步 - M8: RFC 流程规则移入 spec/workflows/rfc-workflow.md，docs/rfcs/README.md 退化为导航； shelved 登记矛盾修正（登记表仅 accepted） - M9: AGENTS.md §2.4 与常用任务入口、CLAUDE.md、docs/README.md、CONTRIBUTING.md、spec/README.md 同步 SIG/RFC 入口 - M10: §4.3 补 Signed-off-by-Agent / Co-Authored-By 与既有审计 trailer 的正交关系 - M11: 校验脚本提取管道容错，坏文件不再静默中断整个校验 - M12: labels 校验改行级精确匹配，防 sig/<name>-xx 词边界绕过 - M13: 豁免一致性判定收紧为"同一单人列表"，与 §4.2 语义对齐（修误报与漏报） - M14: .gitleaks.toml 变更撤出本 PR（与 SIG 主题无关，另行单独 PR） - M15: 脚本加可执行位；另补 nullglob、ERROR 消息文件前缀、kebab 正则统一、 scope_labels 格式与跨文件查重校验、Makefile SIGS_DIR 透传 - 附带：RFC 模板补回滚策略节；§6.3 状态机改引 issue/pr-workflow.md； 试点周期对齐 4 周（第 2 周中期检查点）；label deprecated 操作方式明确； propose 不入 status 枚举的说明 验证：validate-sig-yamls.sh 正向 3 文件通过；负面测试矩阵 8 组全过 （多文件不中断、sig/api-v2 绕过、2 人重叠误报/漏报、scope_labels 非法条目、 跨文件重复映射、空目录等）；无 Go 代码变更，CI lint/test/build 不受影响。 | 1 个月前 | |
fix(review): isolate env-override smoke env, pin no-relogin, mirror in system suite Review fixes for the regression coverage: - pin the default-host resolution with an empty GC_CONFIG_DIR and a cleared GC_HOST, mirroring the Auth Exit Code isolation: a runner whose real config or environment points at a custom host would otherwise bypass the stub token through the StoredToken path and fail loudly but misleadingly - add assert_not_contains (regression-core.sh + tests/system/lib.sh) and assert the dead-end re-login advice is gone, pinning the negative side the docs row claims - mirror the section into tests/system/cases/read/auth.sh so the auth coverage stays 4+4 instead of drifting (layering finding) - REGRESSION.md: boundary sentence for smoke matrix vs tests/system, item 4 describes the isolation, fix pre-existing items 8/9 order to match the script section order Red re-verified with the fixed section: a 5d2e0fb binary exits 1 at the new section under a clean environment; the current tree passes the full script, the system read suite, and the testscript layer. Isolation is proven directly under a hostile GC_HOST. Refs #623 Co-Authored-By: Claude Code <noreply@anthropic.com> | 16 天前 | |
docs(sig): address strict review findings for SIG governance 修复三角色严格评审的 1 blocker + 15 major： - B1: discussion 依赖降级——Phase 1 以带 sig/* label 的 issue 为讨论通道； §6.2 明确平台 repo 级分类能力未验证、启用条件与迁移路径；YAML discussion_category 标注为规划值 - M1: 新增 scope_labels 可选字段（YAML + §5.2 + §6.1）显式映射 scope/* label， 未映射不计入活跃度；评估主体与节奏（sig/governance lead 月度）写入 §3 - M2: 豁免条款闭环——豁免有效期=整改窗口、终态=全部 SIG 脱离、逾期后果 （连续 2 个评估周期未整改触发 degraded 评估）、maintainer 人数判定来源 - M3: §9 补失败判定标准与回退动作清单（收缩 / 撤销单个 SIG / 整体回退） - M4: lazy consensus 补最短公示 ≥ 72 小时 - M5: §3 增加 incubating→archived 试点撤销路径、degraded 量化（lead 缺位 ≥ 2 周对齐 §4.4） - M6: 标注义务封闭集合移除不入库的 .codex-tmp 草稿路径 - M7: source-of-truth-matrix 登记 SIG 元数据与 RFC 流程真相源行；docs-governance §2.2/§3 同步 - M8: RFC 流程规则移入 spec/workflows/rfc-workflow.md，docs/rfcs/README.md 退化为导航； shelved 登记矛盾修正（登记表仅 accepted） - M9: AGENTS.md §2.4 与常用任务入口、CLAUDE.md、docs/README.md、CONTRIBUTING.md、spec/README.md 同步 SIG/RFC 入口 - M10: §4.3 补 Signed-off-by-Agent / Co-Authored-By 与既有审计 trailer 的正交关系 - M11: 校验脚本提取管道容错，坏文件不再静默中断整个校验 - M12: labels 校验改行级精确匹配，防 sig/<name>-xx 词边界绕过 - M13: 豁免一致性判定收紧为"同一单人列表"，与 §4.2 语义对齐（修误报与漏报） - M14: .gitleaks.toml 变更撤出本 PR（与 SIG 主题无关，另行单独 PR） - M15: 脚本加可执行位；另补 nullglob、ERROR 消息文件前缀、kebab 正则统一、 scope_labels 格式与跨文件查重校验、Makefile SIGS_DIR 透传 - 附带：RFC 模板补回滚策略节；§6.3 状态机改引 issue/pr-workflow.md； 试点周期对齐 4 周（第 2 周中期检查点）；label deprecated 操作方式明确； propose 不入 status 枚举的说明 验证：validate-sig-yamls.sh 正向 3 文件通过；负面测试矩阵 8 组全过 （多文件不中断、sig/api-v2 绕过、2 人重叠误报/漏报、scope_labels 非法条目、 跨文件重复映射、空目录等）；无 Go 代码变更，CI lint/test/build 不受影响。 | 1 个月前 |
docs 文档入口
docs/ 是 gitcode-cli 的用户文档目录。
如果你是：
- 使用者：从本目录开始
- 开发者或 AI 协作者：先看 spec/README.md
权威边界
本目录的职责是：
- 解释用户如何使用
gitcode（或源码构建的gc） - 提供命令行为说明
- 提供认证、回归、打包等使用文档
本目录不是项目规则源。
项目正式规则以 spec/README.md 和 spec/ 目录为准。
其中：
- COMMANDS.md 是命令行为唯一真相源
推荐阅读顺序
- INTRODUCTION.md
- COMMANDS.md
- AUTH.md
- LARK.md
- REGRESSION.md
- PACKAGING.md
- AI-GUIDE.md
- LOOP_ENGINEERING_MAINLINE_ANALYSIS.md
- AI-TEMPLATES.md
docs/ai-templates/*.md- 应用案例库
说明：
- AI-GUIDE.md 只服务“外部项目用 AI 操作 GitCode”
- 本仓库内部开发流程请看
AGENTS.md、CLAUDE.md和spec/workflows/* - AI-TEMPLATES.md 提供 gitcode-cli 仓库内部协作模板，不是项目规则源
当前包含内容
| 文档 | 说明 |
|---|---|
| INTRODUCTION.md | GitCode CLI 产品介绍、核心价值、应用场景和快速上手指南 |
| COMMANDS.md | 命令行为说明和示例 |
| AUTH.md | 认证来源和行为说明 |
| LARK.md | 飞书/Lark 通知（lark-cli 集成）安装、配置与发送指南 |
| REGRESSION.md | 核心回归矩阵说明 |
| PACKAGING.md | 本地打包与发布使用说明 |
| AI-GUIDE.md | 外部项目使用 AI 操作 GitCode 的场景指南 |
| SIGS.md | SIG（Special Interest Group）机制介绍与参与指南（规则见 spec/governance/sig-governance.md） |
| rfcs/ | 大型设计提案（RFC）目录与模板（流程规则见 spec/workflows/rfc-workflow.md） |
| LOOP_ENGINEERING_MAINLINE_ANALYSIS.md | 当前主干 Loop Engineering 基因分析与演进计划 |
| AI-TEMPLATES.md | gitcode-cli 仓库内部协作的固定模板 |
| LOOP-GOAL-GUIDE.md | Claude Code /loop 与 /goal 命令在本项目开发流程中的使用指南 |
docs/ai-templates/*.md |
可直接复用的 AI 评论与检查模板文件 |
| Example/ | GitCode CLI 在业务场景中的应用案例和可复制 prompt |