Browsing nixpkgs for something just now and noticed a treewide fix that is probably “wrong” in my local packages. This made me wonder how often things one or more people have taken effort to fix are innocently reintroduced in packages/edits patterned off older examples.
People who’ve made treewide fixes probably have a better sense of whether keeping them from creeping back in is a Sisyphean struggle or not.
I ran a search (https://github.com/NixOS/nixpkgs/search?utf8=✓&q=treewide&type=Commits) for the term to get a sense of how much effort I would need to get current, but there are quite a few, and the first few pages of results suggest a great many duplicate the same logical change(s).
If backsliding into these is an issue (and if they aren’t already being built into the Nix auto-formatter), it might help to have a bot/tool (or at least an auto-generated, de-duplicated checklist with links to examples?) that can flag these and link to a reasonably succinct example of how and why to get it right.
If this thing itself is useful, it might also be helpful if “treewide” commit messages trigger a nudge to the author to ensure the target of the edit makes it into the relevant tools and resources?