Add merge-style support to ward agent pr merge #1215
No reviewers
Labels
No labels
burndown-2026-06
pressure-test
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/ward!1215
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-1202"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This adds merge-style selection to
ward agent pr mergeand teaches the Forgejo merge helper to honor explicit styles or a usable repo default.--styleand forwards it through the read-only broker path.Tests:
ward exec test,ward exec build,pre-commit run --all-files.closes #1202
ward.workflow: pull-request-and-merge
WARDED_WORKFLOW review-note
verdict: block
confidence: high
summary: PR 1215 adds the merge-style flag, repo default-style resolution, broker forwarding, and the expected status/head gates. It does not satisfy the branch-deletion part of ward#1202 because the merge payload ignores the repository default_delete_branch_after_merge setting.
findings:
file: cmd/ward/forgejo_ops.go
line: 574
problem:
mergePullRequestWithHeadAndStylereadsDefaultDeleteBranchAfterMergeintoforgejoRepositoryMergeSettings, but builds the merge request as only{"do": style}plushead_commit_id. It never sends Forgejosdelete_branch_after_mergefield. impact: Repos whose setting says to delete PR branches after merge will not get that behavior throughward agent pr merge, violating the issue requirement to keep branch deletion aligned with the repository default unless ward has a more specific policy. conclusion: Review blocks PR 1215 until the merge request carriesdelete_branch_after_merge` from the repo setting, with test coverage proving both true and false defaults. The merge-style selection itself is close, but this PR should not land while it drops a stated repository merge policy.