4 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Sonnet 5.5	c7c283d34f	feat(tbd_ship): gate auto-merge on the risk tier; unclassified is not low (gitea-mcp#63) ... tbd_ship takes an optional `issue`; the PR is squash-merged only when CI is fully green, the base is not review-protected AND the issue carries exactly one risk/ label, risk/low. No issue, no label, several labels, an unknown value, risk/medium, risk/high or an unreadable issue all fail closed to PR-only with a reason, and the result reports the tier. The zero tier is not low. Tests: gate table incl. every non-low tier, classifyRisk table, end-to-end cases (green+medium, lookup 500/404/403, label case, containment), nine mutants flip-tested red. Limit: the gate enforces the tier of the issue the caller names; it cannot prove it is the right issue. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SZkhi49hfeSqBp5aZJNXsM	2026-10-07 19:36:27 +02:00
mathiasandClaude Opus 4.8	6d344c74a8	feat(tbd_ship): idempotent re-invoke — resume existing branch/PR (#48) ... A second tbd_ship for the same change no longer errors on "branch exists": CreateBranch conflict is tolerated, and if a PR is already open for the head, CreatePullRequest's conflict/validation error resolves it via ListPullRequests (matching head.ref). Identical file content on the branch skips the write, so a resume produces no redundant empty-diff commit. Then the same CI gate runs and merges if now green — so "poll or re-invoke" (the #40 UX) actually works. Test: TestTBDShip_Resume_ExistingBranchAndPR (branch+PR exist, content unchanged → no write, merges when green). First-call paths unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-04 08:30:30 +02:00
mathiasandClaude Opus 4.8	c40a9d9003	test(tbd_ship): cover review-protected + merge-conflict fail-closed paths (#40) ... Adds Call-level tests for the two remaining no-merge paths (green CI but the base requires review, and green CI but the merge returns 409), completing the acceptance matrix alongside the green/pending/red/no-CI cases. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-04 00:41:12 +02:00
mathiasandClaude Opus 4.8	8ebad95adf	feat(tools): add tbd_ship — CI-gated trunk-based ship (#40) ... An intent verb for the trunk-based loop: branch from base → write the file → open a PR → auto-merge (squash) → delete the branch. One call instead of orchestrating file_write_branch + pr_create + workflow_run_status + pr_merge + branch_delete and remembering the conventions each time. The load-bearing safety is a pure, fail-closed CI gate (evaluateShipGate): merge=true ONLY when every workflow run for the PR head commit is completed+success AND the base branch is not review-protected. Every other state — CI pending / red / absent, review-required base, or an unclean merge — fails closed to PR-only and returns the PR with a reason. A change with no CI gate is never auto-merged to trunk (cf. agentsquad#36: non-compiling code reviewer-approved straight to main with no CI wall). - ci_timeout_seconds polls the head commit's runs to completion (default 0 = snapshot, returns pending right after opening the PR). - Derives a deterministic short-lived branch (tbd/<slug>-<hash>); handles new and existing files (fetches the blob sha for updates). - Adds head.sha + mergeable to the PR struct. - Tests: full gate matrix (green/pending/red/cancelled/none/mixed/protected) + Call happy-merge, no-CI fail-closed, red fail-closed, allowlist. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-04 00:40:02 +02:00