diff options
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 3e9c1ca..b2d5617 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md | |||
| @@ -13,18 +13,21 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 | |||
| 13 | - `ngit issue label <id> --label <L> [--label <L>...]` — apply one or more NIP-32 hashtag labels to an existing issue (author or maintainer only); publishes a kind-1985 event; duplicate labels already present via `t` tags or prior kind-1985 events are silently skipped; the new event is saved to the local cache before broadcasting so subsequent reads reflect the change immediately | 13 | - `ngit issue label <id> --label <L> [--label <L>...]` — apply one or more NIP-32 hashtag labels to an existing issue (author or maintainer only); publishes a kind-1985 event; duplicate labels already present via `t` tags or prior kind-1985 events are silently skipped; the new event is saved to the local cache before broadcasting so subsequent reads reflect the change immediately |
| 14 | - `ngit pr label <id> --label <L> [--label <L>...]` — apply one or more NIP-32 hashtag labels to an existing PR (author or maintainer only); publishes a kind-1985 event; duplicate labels already present via `t` tags or prior kind-1985 events are silently skipped; the new event is saved to the local cache before broadcasting so subsequent reads reflect the change immediately | 14 | - `ngit pr label <id> --label <L> [--label <L>...]` — apply one or more NIP-32 hashtag labels to an existing PR (author or maintainer only); publishes a kind-1985 event; duplicate labels already present via `t` tags or prior kind-1985 events are silently skipped; the new event is saved to the local cache before broadcasting so subsequent reads reflect the change immediately |
| 15 | - `ngit account whoami` — show the currently logged-in account(s) | 15 | - `ngit account whoami` — show the currently logged-in account(s) |
| 16 | - `ngit pr` subcommand group: `list`, `view`, `checkout`, `apply`, `send`, `close`, `reopen`, `ready`, `comment`, `merge`; replaces the former top-level `ngit list`, `ngit checkout`, and `ngit apply` commands (hard-migrated); `ngit send` remains at the top level unchanged | 16 | - `ngit pr` subcommand group: `list`, `view`, `checkout`, `apply`, `send`, `close`, `reopen`, `ready`, `draft`, `comment`, `merge`; replaces the former top-level `ngit list`, `ngit checkout`, and `ngit apply` commands (hard-migrated); `ngit send` remains at the top level unchanged |
| 17 | - `ngit pr view <id>` — view a PR with its full details and all comments (author, timestamp, body) in chronological order | 17 | - `ngit pr view <id>` — view a PR with its full details and all comments (author, timestamp, body) in chronological order |
| 18 | - `ngit pr close <id>` / `ngit pr reopen <id>` — change PR status (author or maintainer only) | 18 | - `ngit pr close <id>` / `ngit pr reopen <id>` — change PR status (author or maintainer only) |
| 19 | - `ngit pr ready <id>` — mark a draft PR as ready for review (author or maintainer only) | 19 | - `ngit pr ready <id>` — mark a draft PR as ready for review (author or maintainer only) |
| 20 | - `ngit pr draft <id>` — convert a PR back to draft (author or maintainer only) | ||
| 20 | - `ngit pr comment <id> --body <text>` — post a NIP-22 comment on a PR | 21 | - `ngit pr comment <id> --body <text>` — post a NIP-22 comment on a PR |
| 21 | - `ngit pr merge <id> [--squash]` — merge a PR branch and publish a `GitStatusApplied` event (maintainer only); prints a reminder to push afterwards | 22 | - `ngit pr merge <id> [--squash]` — merge a PR branch and publish a `GitStatusApplied` event (maintainer only); prints a reminder to push afterwards |
| 22 | - `ngit issue` subcommand group expanded: `list`, `view`, `create`, `close`, `reopen`, `comment` | 23 | - `ngit issue` subcommand group: `list`, `view`, `create`, `close`, `resolved`, `reopen`, `comment`, `label` |
| 23 | - `ngit issue view <id>` — view an issue with its full details and all comments (author, timestamp, body) in chronological order | 24 | - `ngit issue view <id>` — view an issue with its full details and all comments (author, timestamp, body) in chronological order |
| 24 | - `ngit issue create --title <T> [--body <B>] [--label <L>...]` — publish a NIP-34 GitIssue event | 25 | - `ngit issue create --title <T> [--body <B>] [--label <L>...]` — publish a NIP-34 GitIssue event |
| 25 | - `ngit issue close <id>` / `ngit issue reopen <id>` — change issue status (author or maintainer only) | 26 | - `ngit issue close <id> [--reason <text>]` — close an issue without resolving it; reason is stored in the event content (author or maintainer only) |
| 27 | - `ngit issue resolved <id> [--reason <text>]` — mark an issue as resolved (kind-1631 `GitStatusApplied`); distinct from close, use when the issue has been fixed; reason stored in event content (author or maintainer only) | ||
| 28 | - `ngit issue reopen <id>` — reopen a closed or resolved issue (author or maintainer only) | ||
| 26 | - `ngit issue comment <id> --body <text>` — post a NIP-22 comment on an issue | 29 | - `ngit issue comment <id> --body <text>` — post a NIP-22 comment on an issue |
| 27 | - `ngit issue list` command: lists NIP-34 issues with their status; supports `--status` (comma-separated: open,draft,closed,applied; default: open), `--hashtag` (comma-separated label filter), `--json`, `--offline`, and an optional `<id>` positional argument to show full details of a specific issue; hashtags are shown at the end of each row | 30 | - `ngit issue list` command: lists NIP-34 issues with their status; supports `--status` (comma-separated: open,draft,closed,applied; default: open), `--label` filter, `--json`, `--offline`, and an optional `<id>` positional argument to show full details of a specific issue |
| 28 | - `nostr.repo-relay-only` git config key: when set to `true`, nostr events are sent only to the repository's own relays, skipping the user's personal write relays and default/blaster relays; set persistently via `git config nostr.repo-relay-only true` or in one step with `ngit init --repo-relay-only` | 31 | - `nostr.repo-relay-only` git config key: when set to `true`, nostr events are sent only to the repository's own relays, skipping the user's personal write relays and default/blaster relays; set persistently via `git config nostr.repo-relay-only true` or in one step with `ngit init --repo-relay-only` |
| 29 | 32 | ||
| 30 | ## [2.2.3] - 2026-02-27 | 33 | ## [2.2.3] - 2026-02-27 |