One way I force people (mostly myself) to include shebang lines:
Have a scripts directory in my repo that mixes shell and python scripts with no file extensions and executable bits set. If I don't put a shebang, it just doesn't run.
Of course, this requires you to have firm control of code style policies.
Make a post-commit hook that adds "#!/usr/bin/yes No." at the top of every file missing a shebang.
Heh.
But, does shebang works when you want to source some files?
you can source a file that contains a shebang in most (all?) shells assuming it contains code written in the same shell language. I.e. a bash file can't source a fish file and vice-versa.
I fix what I can, but it's like mopping up water during a rainstorm. Yes it's better than doing nothing, but also there will be more in twenty minutes so don't make any plans.