guard: the git write functions call the guard #659
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#665 guard: refuse every commit on the default branch after the first push, with no override
sixfold-space/madtea
#669 guard: a parity test fails when a write skips the guard
sixfold-space/madtea
#670 epic: one guard enforces the recorded limits on every surface
sixfold-space/madtea
#653 guard: add the guard package with its three effects
sixfold-space/madtea
Reference
sixfold-space/madtea#659
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
What to build
The push and commit functions in
internal/gitreceive 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, inservice/git,service/workflow, andservice/orchestrate.Depends on
Acceptance
pushrefuses the default branch on the CLI and MCP.commitrefuses the default branch through the guard.finishstill refuses the default branch, and the first push into an empty repo still works.