pudl.scripts.pyrefly_diff_baseline#
Diff the pyrefly baseline against a git ref by content, not by raw JSON text.
Functions#
|
Load baseline error entries from a git ref, or the working tree if |
|
Diff a pyrefly baseline against a git ref by (file, code, description). |
Module Contents#
- pudl.scripts.pyrefly_diff_baseline._load_baseline_entries(ref: str | None, baseline_path: pathlib.Path) set[tuple[str, str, str]][source]#
Load baseline error entries from a git ref, or the working tree if
refis None.
- pudl.scripts.pyrefly_diff_baseline.main(ref: str, baseline_path: pathlib.Path) None[source]#
Diff a pyrefly baseline against a git ref by (file, code, description).
Run this after
pixi run pyrefly-prune-baselineandpixi run pyrefly-update-baselineto sanity-check the regenerated baseline before committing it: the “fixed” list should match what you intentionally fixed, and the “newly baselined” list should only contain pre-existing issues you’re deliberately deferring – not something your own change introduced.A pyrefly version bump can also surface “newly baselined” entries that are purely description-text reformatting of an existing error rather than a real new one; check the file and error code before assuming it’s a regression.