npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/bin/ngit/sub_commands/comment.rs, branch v2.4.2

fix(comment): pass git_repo to login so local config takes precedence

2026-03-05T15:36:21+00:00

publish_comment was calling login_or_signup with &None for git_repo, causing the GitLocal source to be skipped entirely. This meant the global git config (including any bunker-uri) was used instead of the local nsec, ignoring the local login. Pass the discovered Repo through CommentArgs so local config correctly takes precedence over global.

add NIP-21 content tags (q/p) to issues, comments, PRs and patches

2026-03-04T16:24:29+00:00

- parse nostr: URI mentions in issue bodies, comment bodies, PR descriptions, patch commit messages and cover letters - npub/nprofile mentions produce p tags; note/nevent/naddr mentions produce q tags per NIP-22 - naddr q tag value uses raw :: format - nevent pubkey field populated from embedded author or local cache lookup - dedup_tags() removes duplicate p tags and suppresses q tags whose event-id is already covered by an existing e threading tag - all parsing errors are non-fatal: invalid nostr: tokens are skipped

fix NIP-22 compliance and add --reply-to flag for issue/PR comments

2026-03-04T15:09:54+00:00

- Add missing P and p tags (root and parent author pubkeys) - Fix E tag 4th element to be root pubkey (was empty string) - Fix e tag 4th element to be parent pubkey (was "reply", a NIP-10 convention) - Add --reply-to flag to both issue and PR comment commands - When --reply-to is set, look up the parent comment from cache and use it as the parent scope (e/k/p); root scope (E/K/P) always stays the issue/PR - When --reply-to is omitted, parent == root (existing top-level behaviour)

restructure CLI around ngit pr/issue subcommand groups

2026-03-04T14:50:01+00:00

Introduce ngit pr subcommand group (list, view, checkout, apply, send, close, reopen, ready, comment, merge) replacing the former top-level ngit list/checkout/apply commands. ngit send is kept at the top level. Expand ngit issue with view, create, close, reopen, comment subcommands. Status changes (close/reopen/ready) are gated to the PR/issue author or a repository maintainer. ngit pr merge is maintainer-only and publishes a GitStatusApplied event immediately after the git merge.