- issue +comment --reply-to <id>: reply to an existing comment; the
server requires both parent_id and reply_id, so both are set
- issue +comment-replies: list a comment's replies via the
children_journals endpoint with --page/--limit
Production-verified: parent -> reply -> list replies -> delete
round-trip on a real issue. 3 new unit tests and bilingual docs.
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Completes issue comment CRUD on top of the existing issue +comment by
covering the v1 journals endpoints (index/update/destroy):
- issue +comments: list comments with --category/--keyword filters and
--page/--limit pagination
- issue +comment-edit: PATCH a journal's notes by --comment-id
- issue +comment-delete: DELETE a journal by --comment-id
--comment-id is validated as an integer before any API call.
Production-verified against gitlink.org.cn: full create -> list ->
edit -> delete round-trip on a real issue. Includes 6 unit tests,
bilingual README examples, and en-US/zh-CN i18n keys.
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Resolved conflicts with i18n infrastructure from PR #95 and metadata
lookup shortcuts from PR #43.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The API returns both "id" (global database PK) and "project_issues_index"
(per-project sequential number). The +list JSON output was a raw API
pass-through, making the database ID the most prominent identifier.
This change normalizes each issue in the list:
- Add "number" field from project_issues_index (matches the web URL)
- Rename "id" to "database_id" to prevent confusion
The "number" field now matches the --number flag used by +view, +close,
+update, and +comment commands.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
1os21ka23r9navae6mrro
Mengz
wbtiger
whzy
Zhang Jinnan