This might be dependent on the size of your codebase, but it can be useful to start by running checks locally, using the static analysis to find bugs, then subm

This might be dependent on the size of your codebase, but it can be useful to start by running checks locally, using the static analysis to find bugs, then submitting the fixes independent of the static analysis. That way, by the time you propose enabling static analysis on all commits, it doesn’t scare people away. Granted, this has the potential of the opposite problem, convincing detractors that static analysis didn’t find much, but that can be avoided by keeping a list of the bugs that were resolved ahead of time.