Require status checks to pass to avoid regression

[Kilo59]

I've noticed that some previous fixes have creeped back into the codebase even though the travis build was failing them.

If not already I think we ought to require the Travis CI status check to pass.
I understand that the travis builds have been quite flakey and I'm attempting to address that as well #598.

I also think this is probably a good idea before we start automating the deployment process.

[CamDavidsonPilon]

Thanks for the suggestion, @Kilo59. My concern is that this disrupts workflows (ex: commiting small PRs off a branch that is failing). However, this could be solved with a pre-commit hook on my side. Let me think about it a bit more.

[Kilo59]

😄 Yeah, I totally understand the concern.
Hopefully, this PR #598 can address some (probably not all) of that.

As admin you would still be able to force things through, but it would be 1 extra step, and ONLY admins would have that power.