The recent python reformatting has shown that people are eager to have a uniform style already. Even though nixfmt isn't fully stable yet, we can already go ahead and use it to reformat all of Nixpkgs. With future nixfmt changes it can be reformatted again.

• shell.nix/direnv integration: Development shell with a pinned nixfmt #322512

• Make sure --verify succeeds: Use --verify in Nixpkgs diff CI nixfmt#215

• Change the workflow to only enforce formatting of new/changed files, and do the first formatting pass

  • This prevents the problem of breaking master when merging an older PR that introduces a new files and succeeded CI from before the formatting was enforced by CI
  • Enforce nixfmt on new files and changed files that were already formatted #326407

• Fix [Tracking issue] remove all src = ./. entries that unintentionally include their own .nix files #301014

• Wait until after the current release, minimise the number of conflicts (by picking a time with minimal open PRs)

• [ ] Have better integration

  • Make treefmt, nix fmt work
  • Fix Remove recursive mode nixfmt#151 beforehand
  • We don't need this for now, see flake: configure nix fmt #325575 (review)

• [ ] Have an easy maintainer script to rebase PRs with formatting: Script to rebase with formatting nixfmt#159
  Not a blocker

• Open an issue/discourse post with information on the nixfmt reformatting

• Format all actively developed branches (master, release-, staging-? (ask staging maintainers)) at the same time to avoid all backporting problems

• [ ] Figure out how to do future reformats and nixfmt updates (pin it, probably separately from the main package)
  Not a blocker

• [ ] Make sure there's no problems with generated files

  CI will complain when they get updated without being formatted, which gives a good signal to the PR author that they need to either manually format, or implement the formatting in the generator