| Files | Last commit | Last update |
|---|---|---|
feat(discussions): add repo discussion comment edit/reply Implements repo-level discussion comment write commands: - gc discussions project comments edit <number> <comment-id> [-R] --body [--json] - gc discussions project comments reply <number> <comment-id> [-R] --body [--json] API alignment per the official OpenAPI: - UpdateRepoDiscussionComment uses PUT, not PATCH Docs: docs/COMMANDS.md gains sections for both commands. Tests: flag parsing, run validation, HTTP-mocked request assertions (method/path/body), --json output, and API error paths. Refs #552 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> | 1 month ago | |
feat(discussions): add repo discussion create/edit commands Implements repo-level discussion write commands: - gc discussions project create [-R owner/repo] --title --category --body [--json] - gc discussions project edit <number> [-R owner/repo] [--title/--body/--category] [--json] API alignment per the official OpenAPI: - CategoryName field on repo create/update discussion options (category is required when creating a discussion) - UpdateRepoDiscussion uses PUT, not PATCH Docs: docs/COMMANDS.md gains sections for both commands. Tests: flag parsing, run validation, HTTP-mocked request assertions (method/path/body), --json output, and API error paths. Refs #552 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> | 1 month ago | |
feat(discussions): add API write operations and repo discussion delete command Add all 30 discussion write operation API functions (15 org + 15 repo) and repo discussion delete command. Closes #562 | 2 months ago | |
fix(discussions): guard empty edit body in project edit Reject empty --body/--body-file in discussions project edit (no-op PUT guard), matching the comments commands and the org-level edit fix. Refs #552 | 1 month ago | |
feat(cli): 统一 list 命令分页 flag（--limit + --per-page 全覆盖） issue #501：list 类命令分页 flag 命名分裂——issue/label/milestone/ repo list/repo log 仅 --limit；discussions(org+project) 仅 --per-page； pr list/actions 两者并存。agent 无法预知某命令用哪个 flag（§6.1）。 方案 A：所有 list 命令统一提供 --per-page(API page size)+ --limit (客户端结果上限,默认 30)。语义对齐 pr list 既有双 flag 模式 (resolvePerPage + trim + LimitSet/PerPageSet)。 改动： - issue/label/milestone/repo list/repo log（5 命令）补 --per-page + resolvePerPage/trim + PerPage<0 校验 - discussions list(org) + project list（2 命令）补 --limit + trim + Limit<=0 校验 - pr list / actions（已合规）不改 - docs/COMMANDS.md 更新 7 命令分页 flag 说明（修正 label list 旧误述） - 单测：issue list 补 resolvePerPage/trim/validation 表驱动测试； discussions org+project 修 fixture(Limit:30) + 补 limit 校验用例 §5.9.B：已查 gc-api-doc 确认 issues/labels/milestones 端点均支持 per_page（无功能缺口，仅 flag 命名分裂）。 Closes #501 | 2 months ago | |
refactor(discussions): DRY print helpers into render package org/project list+view 的 printDiscussions/printDiscussion 是逐字节复制 （~33+24 行 ×2），未来格式变更需改 4 处。抽取 PrintDiscussions/ PrintDiscussion 到已有的 pkg/cmd/discussions/render 包，4 个调用点统一 引用，删除本地副本。 行为 bit-identical：函数体原样搬迁，仅包名/调用方变化。 Closes #500 | 2 months ago | |
feat(discussions): add repo discussion create/edit commands Implements repo-level discussion write commands: - gc discussions project create [-R owner/repo] --title --category --body [--json] - gc discussions project edit <number> [-R owner/repo] [--title/--body/--category] [--json] API alignment per the official OpenAPI: - CategoryName field on repo create/update discussion options (category is required when creating a discussion) - UpdateRepoDiscussion uses PUT, not PATCH Docs: docs/COMMANDS.md gains sections for both commands. Tests: flag parsing, run validation, HTTP-mocked request assertions (method/path/body), --json output, and API error paths. Refs #552 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> | 1 month ago |