overview / rules / baseline-branch-discard
baseline-branch-discard
Force-deleting a branch no remote holds discards those commits with no way back.
what it refuses, and what it lets through
In one line, from native/baseline.h: git branch -D of a tip no remote holds.
-d is safe: git refuses it on an unmerged branch. -D / --delete --force override that check, so the loss is a tip no remote holds, whatever the branch is called (a local main with a remote comes back by checkout).
From the comment in native/baseline.h above the code that decides it.
the refusal, as the agent reads it
rabadon BLOCKED this action.
Rule: baseline-branch-discard — force-deleting a branch no remote holds discards those commits with no way back
git branch -D '<branch>' — its tip <tip sha> is on no remote. push it, or use `git branch -d <branch>` which git allows once the work is merged
Adjust the approach instead of retrying the same action.
(only the user can override this: they may add "baseline-branch-discard" to disabled[] in .rabadon/guard.json or run `rabadon off`. If this rule looks wrong for the task, stop and ask the user; do not switch supervision off yourself.)
Rendered from the strings in native/baseline.h and the envelope in native/gate_pre.h (Judge::refuse). A word in <angle brackets> is filled in from the command at the moment it is refused.
in watch mode the same verdict is recorded, and nothing is stopped
rabadon (watch) would have blocked this.
Rule: baseline-branch-discard — force-deleting a branch no remote holds discards those commits with no way back
git branch -D '<branch>' — its tip <tip sha> is on no remote. push it, or use `git branch -d <branch>` which git allows once the work is merged
Nothing was stopped. `rabadon on` makes this a real refusal.
switching it off
Only the user can switch it off, by id, in the project's guard:
{ "disabled": ["baseline-branch-discard"] }
or by pausing supervision with rabadon off, which records the change. Every other rule keeps running.
in the field
No record in the published field dataset (field.jsonl, 778 records, 2026-07-27 to 2026-08-26) carries this id.
The dataset is on the field page.