guard: the git write functions call the guard #659

Closed
opened 2026-09-29 16:39:56 +00:00 by hexajon · 0 comments
Owner

What to build

The push and commit functions in internal/git receive the guard as an interface when they are built, and call it before they write. A writer with no guard refuses every write. Today each push path carries its own checks, in service/git, service/workflow, and service/orchestrate.

Depends on

  • #653, because the guard package must exist first.

Acceptance

  • push refuses the default branch on the CLI and MCP.
  • commit refuses the default branch through the guard.
  • finish still refuses the default branch, and the first push into an empty repo still works.
  • The orchestrate revert still pushes its revert branch and opens a PR.
  • Breaking for anyone who pushes the default branch through madtea. The release notes say so.
## What to build The push and commit functions in `internal/git` receive the guard as an interface when they are built, and call it before they write. A writer with no guard refuses every write. Today each push path carries its own checks, in `service/git`, `service/workflow`, and `service/orchestrate`. ## Depends on - #653, because the guard package must exist first. ## Acceptance - `push` refuses the default branch on the CLI and MCP. - `commit` refuses the default branch through the guard. - `finish` still refuses the default branch, and the first push into an empty repo still works. - The orchestrate revert still pushes its revert branch and opens a PR. - Breaking for anyone who pushes the default branch through madtea. The release notes say so.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
sixfold-space/madtea#659
No description provided.