split-run
An advisory by default: it explains, and blocks nothing, on the same target run again on a different project set, as a separate call.
What it catches
The same target run again on a different project set, as a separate call.
Why
magus run and magus affected take one target and many projects, so the same target run twice on two project sets is usually one call typed as two: magus run lint . docs covers what magus run lint . and magus run lint docs would otherwise cost as two workspace loads. It compares the session's last magus run/affected invocation against this one: same target, same charms, a different project set, inside a ten-minute window. The one-line shape (magus run lint . && magus run lint docs) is chained-run's, which refuses it and names the combined call. Charms count as part of the target identity, so lint and lint:rw are never combined into one call. Held to one firing per session.
Default and override
By default this rule takes the decision advise. A workspace sets it by name, in its root
magusfile, to advise or off:
magus\guard.builtins({"split-run": "off"})
A loosening takes effect once it is committed; a tightening applies at once.
Seeing it
A verdict names its rule in brackets, which is how you got here:
advise [split-run]: ...
magus describe rule split-run 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
- Setting a built-in rule - how a workspace changes this default