gitea-axi/.claude/tasks/0010-pr-create-and-comment.md at 3446ce33a52276142b80c2dd723fc38b045051f7

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

2.0 KiB

Raw Blame History

spec, blocked-by

spec	blocked-by
gitea-axi	0004-issue-create-and-comment

What to build

pr create and pr comment. pr create takes --title (required), --body/--body-file, --base, --head, --assignee, --reviewer, repeatable --label (name-resolved), and --milestone (name-resolved); --draft and --project are excluded (no Gitea API support). When --head is omitted it defaults to the current local branch from git; when --base is omitted it defaults to the repository's default branch fetched from the repo endpoint. Idempotent: before creating, check for an existing open PR for the same base/head pair; if found, return pull_request: { number, url, already: true } instead of creating a duplicate. Success output is the action block created: { number, url } — action block when the mutation ran, entity block when it was a no-op. pr comment <n> posts through the shared issue-comment endpoint and returns the created comment as comment: { number, author, created, body } (800-char truncation), diverging from gh-axi's status-only block to save a follow-up view call (see ADR 0008).

Acceptance criteria

pr create --title creates a PR and outputs created: { number, url }
Omitted --head resolves to the current local branch; omitted --base resolves to the repo's default branch
An existing open PR for the same branch pair short-circuits to pull_request: { number, url, already: true } with no duplicate created
--label and --milestone resolve names case-insensitively with VALIDATION_ERROR on unknown names; --assignee and --reviewer pass through
pr comment <n> --body outputs comment: { number, author, created, body } from the POST response, body truncated at 800 chars
Missing required inputs (--title on create, body on comment) fail with VALIDATION_ERROR (exit 2) before any API call
Fixture-server tests cover creation with defaults, the idempotent short-circuit, name resolution failures, and the comment output shape

2.0 KiB Raw Blame History

What to build

Acceptance criteria

2.0 KiB

Raw Blame History