I recently had to revert a commit because deploying it on the production server failed when running collectstatic, even though all the tests and github actions passed.

The issue is that the production server uses ManifestStaticFilesStorage for its static files, which adds a post-processing step the the collectstatic command and that step will crash with a ValueError if a missing static file is referenced (in my case, a minified javascript file had a comment referencing a .map file that had been deleted).

This type of issue should be caught early so we can fix it during the PR and avoid a revert.