magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

worktree-remove

A deny rule: it refuses removing a worktree, which may hold another session's uncommitted work, and names what to run instead.

What it catches

Removing a worktree, which may hold another session's uncommitted work.

Why

A worktree is where another session may be working right now, and its uncommitted changes live nowhere else. Check it is clean first with git -C <path> status, and remove it only once you know what it holds.

Seeing it

A verdict names its rule in brackets, which is how you got here:

deny [worktree-remove]: ...

magus describe rule worktree-remove prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

  • All rules - what this workspace enforces, deny first
  • The guard - how a verdict is reached and wired
guardrulesworktree-removedeny
Last updated (d966bfce)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Session

An agent host's conversation, by the id the host delivers to its hooks. magus never mints one: a record with no session is unattributed, and the OS user it carries says whose account ran it.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate.

Conventions

Placeholders

Angle brackets mark a value you replace with your own - never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.