4 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Sonnet 5.5	6efd309159	fix(merge gate): bind pr_merge and tbd_ship merges to the head commit the gate checked (TOCTOU) ... The gate evaluates CI for one head sha; a push to the PR branch between that check and the merge would have merged unchecked code. MergePRArgs now carries head_commit_id (documented in Gitea 1.27.1's MergePullRequestOption) and both tools send the sha they evaluated. Tests for both tools; each removal flip-tested red. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SZkhi49hfeSqBp5aZJNXsM	2026-10-08 08:12:45 +02:00
mathiasandClaude Sonnet 5.5	c3d8401604	feat(pr_merge): gate it like tbd_ship — green CI, unprotected base, exactly one risk/low issue (gitea-mcp#74) ... pr_merge was an independent merge path with no CI, protection or tier check. It now reads the PR, the base's branch protection and the head commit's CI runs, takes the tier from the issue named in `issue`, and runs the same evaluateShipGate as tbd_ship (helpers shared, not copied). A refusal is a result (merged:false, reason, ci_status, risk); an unreadable PR or protection probe is an error; a merge conflict is still an error. Above risk/low a human merges in the UI. Tests: tier table, no-issue, issue lookup failures, CI and protection not overridden by risk/low, read-side failures, tier read from the named issue only; nine wiring mutants flip-tested red. Shared reason text now says "PR left open" (the PR already exists for pr_merge). Behaviour change: pr_merge without `issue`, or on a PR with no green CI, merges nothing. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SZkhi49hfeSqBp5aZJNXsM	2026-10-08 08:11:40 +02:00
mathias	d3faffc4c4	feat(tbd_ship): gate auto-merge on the risk tier; unclassified is not low (#63) (#73) ... Co-authored-by: Mathias <mthbqv@gmail.com>	2026-10-08 06:02:34 +00:00
mathiasandClaude Opus 4.8	1eceb5f7fe	ci(cd): skip docs-only pushes; move HOW_GITEA_MCP_WORKS into docs/ ... Relocate the doc under docs/ and add paths-ignore: ['docs/**'] to the CD push trigger so documentation-only changes no longer rebuild the image and roll the pod. Branch pushes with only docs/ changes are skipped; tag (v*) pushes and any push touching code still deploy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-07 00:43:46 +02:00