feat(guard)!: #665 refuse every default-branch commit, with no override #776
No reviewers
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.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!776
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-665-commit-no-override"
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?
Summary
madt_commit and madtea commit now refuse a commit on the default branch with no
override: the allow_default_branch MCP parameter and the --allow-default-branch
CLI flag are removed with no alias, and the merge/revert/cherry-pick in-progress
exemption is gone (ADR 0006, ADR 0046). Only the first commit in an empty repo
stays exempt, keyed on git state, not config. The refusal names the
feature-branch next step. Two own-repo completion tests that committed on main
move to a feature branch - a direct consequence of removing the in-progress
exemption.
Refs #665