guard: a parity test fails when a write skips the guard #669
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
#670 epic: one guard enforces the recorded limits on every surface
sixfold-space/madtea
#659 guard: the git write functions call the guard
sixfold-space/madtea
#660 guard: the forge client send functions call the guard
sixfold-space/madtea
Reference
sixfold-space/madtea#669
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?
ADR 0046 says that a forge client or a git writer built with no guard refuses every write, and that a parity test fails when production code builds one with no guard, or sends a write around the guarded functions.
Scope:
internal/parityfails when production code builds a forge client or a git writer with no guard.Acceptance:
internal/gitfails the test.Depends on #659 and #660. Decision record: ADR 0046.
The v0.20.0 breaking set is complete and green on main. The code landed across the v0.20.0 branches, the full local gate passes, and the forge suite is green on both forges at both pinned versions on current main (
31693766). Closing as done.