gitea-axi/.claude/tasks/0011-pr-edit-close-reopen.md at 5e66b4d7466a435547b798e9d76aaae181646b2e

Files

alexion d03a079854 docs: adopt Conventional Commits and land planning docs

- CONVENTIONAL-COMMITS.md: vendored spec (v1.0.0); CLAUDE.md requires
  agent-written commits to follow it
- tasks 0002-0020: remaining task breakdown of the gitea-axi spec
  (0019 reframed around the three-tier test taxonomy: unit,
  integration, end-to-end)
- spec, CONTEXT.md, and ADRs 0006/0007/0011: pending design
  refinements from the planning sessions

2026-07-11 07:14:39 -04:00

1.9 KiB

Raw Blame History

spec, blocked-by

spec	blocked-by
gitea-axi	0005-issue-edit-close-reopen

What to build

The PR-side state mutations: pr edit, pr close, pr reopen, mirroring the issue-side slice with two PR-specific differences. pr edit <n> supports --title, --body/--body-file, --add-label/--remove-label (same additive-endpoint and lookup rules as issues), --add-assignee/--remove-assignee (fetch-then-patch), --add-reviewer/--remove-reviewer, --milestone (name-resolved), and --base. Reviewer mutations cannot use fetch-then-patch — EditPullRequestOption has no reviewers field — so they go through Gitea's dedicated requested-reviewers POST/DELETE endpoints (see ADR 0007 amendment). pr close <n> supports --comment with the same two-call partial-failure policy as issue close, and returns pull_request: { number, state, already: true } when already closed or merged. pr reopen <n> returns pull_request: { number, state: "open", already: true } when already open. Success outputs follow the action-block pattern: edited:/closed:/reopened: with { number, status: "ok" }.

Acceptance criteria

pr edit applies title, body, milestone, and base changes and outputs edited: { number, status: "ok" }
Label and assignee mutations follow the same rules as issue edit (additive endpoints, fetch-then-patch, unapplied-label silent success)
--add-reviewer/--remove-reviewer call the requested-reviewers endpoints with { reviewers: [login] }
pr close --comment posts the comment after the PATCH and surfaces a comment failure; closing an already-closed-or-merged PR returns the entity block with already: true
pr reopen on an open PR returns the entity block with already: true; otherwise outputs reopened: { number, status: "ok" }
Fixture-server tests cover reviewer add/remove, the merged-PR close no-op, and the reopen paths

1.9 KiB Raw Blame History

What to build

Acceptance criteria

1.9 KiB

Raw Blame History