meaning of --fatal-warnings
Right now, passing
--fatal-warnings makes the process stop on the first warning, and not passing it results in the generation continuing to the end (potentially finding other warnings) but still have a non-zero exit code.
One could argue that warnings are considered fatal either way: Is this intentional? would you consider a mode where warnings don't cause the build to fail?