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

revert-classify

An advisory: it explains, and blocks nothing, on a revert that has not classified what it is reverting.

What it catches

A revert that has not classified what it is reverting.

Why

Reverting regenerated output is the wrong default. An agent that did not hand-edit a gen/ file concludes it is not "its" change and discards it, but a generate target rewriting its declared outputs is the system working, and those outputs belong in the same commit as the source that moved them. The honest test is whether the SOURCE changed, not whether anyone typed into the output. Revert only when regenerating reproduces the same diff with the target's declared inputs unchanged; that drift is environmental and worth reporting rather than discarding.

Seeing it

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

advise [revert-classify]: ...

magus describe rule revert-classify 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
guardrulesrevert-classifyadvise
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.

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. See targets.

Advisor

One read-only check from the advice suite: it reads the changeset through magus and writes one titled section of findings. The same advisors run as a pull request comment in CI and inside magus diff --impact locally.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.