| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2026-03-05 | feat(status): add --reason to all pr and issue status commands | DanConwayDev | |
| All status transitions (pr close/reopen/ready/draft, issue close/reopen/ resolved) now accept an optional --reason flag stored in the event content. | |||
| 2026-03-05 | feat(status): add pr draft, issue resolved, and --reason for issue close | DanConwayDev | |
| Add `ngit pr draft <id>` to convert a PR back to draft (kind-1632). Add `ngit issue resolved <id> [--reason <text>]` to mark an issue as fixed (kind-1631 GitStatusApplied), distinct from close which signals wontfix/duplicate/invalid. Add `--reason <text>` to `ngit issue close` — stored in event content. Also fix success/error message wording in pr_status and issue_status to use consistent past-tense action strings. | |||
| 2026-03-04 | restructure CLI around ngit pr/issue subcommand groups | DanConwayDev | |
| 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. | |||