zzx-coder
/
gitlink-cli
forked from Gitlink/gitlink-cli
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases 8 Wiki Activity
142 Commits 12 Branches 18 Tags 40 MiB
Commit Graph

13 Commits

Author SHA1 Message Date
15972095207 84e3a37daa 1 2026-06-09 08:04:41 +08:00
15972095207 97f9f63645 fix: use --label clear to remove labels from issue 
Empty string doesn't work as CLI flag value. Use 'clear' keyword instead:
- --label 327264,327265  set labels
- --label clear          remove all labels

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 09:12:44 +08:00
15972095207 c8b4eb2ea0 feat: add --label support to issue update command 
Support setting or clearing labels on existing issues:
- --label 327264,327265  set labels
- --label ""            clear all labels

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 09:10:15 +08:00
15972095207 ed7a2bbcd6 feat: support multiple labels in issue create (--label id1,id2) 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 08:59:33 +08:00
15972095207 7f53548244 fix: use correct issue_tag_ids field for issue create --label 
The GitLink v1 API expects issue_tag_ids (array of integers), not label_id.
This fixes the bug where --label was silently ignored when creating issues.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 08:50:37 +08:00
zhangqing 1e32e12145 feat: add notification module + fix issue --label bug 
- Add notification +list, +view, +read, +delete commands
- Add notification unit tests
- Register notification module in register.go
- Fix issue +create ignoring --label flag

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
 2026-06-02 15:08:53 +08:00
wangyue789 23a478bd69 feat(issue): add authors shortcut 2026-05-25 08:50:47 +08:00
wangyue789 9638d279d3 feat(issue): add assigners shortcut 2026-05-25 08:49:41 +08:00
Tiger 64c0ff3cb5 Normalize issue +list output to use project-level issue numbers 
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>
 2026-05-24 01:00:31 +08:00
wangyue789 b2e840f498 feat(issue): add batch close shortcut with dry-run support 2026-05-13 17:27:50 +08:00
wbtiger 44147bd71a fix: Issue 操作切换到 v1 API，统一使用 project_issues_index 替代数据库 ID 
改动：
- Issue 所有操作（list/view/create/update/close/comment）从旧版 /api/ 切到 /api/v1/
- flag --id/-i 改为 --number/-n（与网页 URL 中的 Issue 编号一致）
- create 增加 status_id:1（必填，v1 API 要求）
- update/close 的 HTTP 方法从 PUT 改为 PATCH（v1 API 规范）
- comment 的请求字段从 content 改为 notes（v1 API 字段名）
- comment 路径从 /issues/{id}/journals 改为 /v1/{owner}/{repo}/issues/{number}/journals

Fixes #9
 2026-05-12 16:55:23 +08:00
Zhang Jinnan 46aa383d76 fix: preserve issue description on updates 2026-04-28 08:43:51 +08:00
wbtiger e892370de8 init gitlink-cli 2026-04-17 10:01:30 +08:00