From d4dd5aad3e8b2cf2caa42faed37ea7738ad510ae Mon Sep 17 00:00:00 2001 From: lexis Date: Mon, 22 Jun 2026 23:32:14 +0200 Subject: [PATCH] docs(tools/forge): document read-before-comment guard + --force flag --- docs/tools/forge.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/docs/tools/forge.md b/docs/tools/forge.md index 42e50906..f68908b0 100644 --- a/docs/tools/forge.md +++ b/docs/tools/forge.md @@ -31,14 +31,15 @@ hive-forge issue close 42 # close an issue (kind-validated) hive-forge pr status --pr 42 # PR health (mergeable / CI / reviews) hive-forge issue create --title "..." --body "..." # --- flat aliases below remain valid (hidden) --- -hive-forge view 42 # title + body + comments -hive-forge comments 42 # list all comments (human-readable) +hive-forge view 42 # title + body + comments (marks thread read) +hive-forge comments 42 # list all comments (human-readable; marks thread read) hive-forge comments 42 --tail 10 # last 10 comments (count-then-page; efficient on long threads) hive-forge --json comments 42 # same as above, JSON array (global flag) hive-forge comment 42 --body "..." # post comment (inline body) hive-forge comment 42 --body-file - <` or + `hive-forge comments ` (which mark the notification read and clear the + block), or pass `--force` to skip the guard. - `comment --body "..."` with backticks in the body: always use `--body-file -` with a HEREDOC to avoid shell escaping issues. - `pr-create --push` also runs `git push forge ` and suppresses