| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
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): add missing no-leak assertion, guidance floor, and doc wording - status integration test now actually asserts the env token value never appears in stderr; the previous delta report claimed this assertion existed but it did not (caught by the test review) - login integration test pins the warning header independently of the computed guidance block, so an empty-EnvVars regression cannot pass vacuously through Contains("") - COMMANDS.md: the disable step is reversible on Unix but a deletion on Windows user scope, and the auth model reference is now a link Refs #613 Co-Authored-By: Claude Code <noreply@anthropic.com> | 17 天前 | |
refactor: move config from internal/ to pkg/ to fix layering Move internal/config → pkg/config to resolve the layering violation where pkg/cmdutil (shared pkg/ layer) imported internal/config (private internal/ layer). The config package is used by 16 files across all command packages and is inherently a shared component. Change: update all import paths from internal/config to pkg/config. No logic changes — pure mechanical refactor. Fixes #351 Co-Authored-By: Claude <noreply@anthropic.com> | 4 个月前 | |
feat(auth): disclose git-credential follow-up limitation in setup-git Refs #529 | 2 个月前 | |
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(auth): require interactive token disclosure | 4 个月前 | |
feat(auth): add gc auth setup-git credential helper Refs #529 | 2 个月前 |