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

interpreter-rewrite

A deny rule: it refuses an inline interpreter rewriting a file this tree already carries, and names what to run instead.

What it catches

An inline interpreter rewriting a file this tree already carries.

Why

A python -c or node -e that reads a tracked file, substitutes, and writes it back is an edit nobody reviewed: it lands before a diff exists, and the script that produced it is gone the moment the line ends. The editor tool reads the file first and reports what it changed, which is the same edit with a record of itself. It fires on the WRITE, not the interpreter: a one-liner that computes something, prints it, or creates a file the tree does not carry is untouched, and so is anything under a scratch path.

Seeing it

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

deny [interpreter-rewrite]: ...

magus describe rule interpreter-rewrite 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
guardrulesinterpreter-rewritedeny
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.

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

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