Maybe he just doesn't like what you're selling. Find out what direction the company wants to go and help them get closer to that. I would recommend temporary f

Maybe he just doesn't like what you're selling. Find out what direction the company wants to go and help them get closer to that. I would recommend temporary feature branches, that frequently merge into master and also release branches for the code that you want to push to production. You can always do hotfix branches off of the release branch. There's always that wet dream of no branches at all, every edge case automatically tested and pushing right to production if the tests pass. But this is really not practical for most places of business. But if you can promote some meaningful amount of: 1) Unit tests 2) Integration tests 3) Functional tests That automatically run when code is pushed, that's a good first step. Also, if you can get them on a regular release cadence of monthly or better, that would also be preferable, and you should be able to release code to pretty much any environment with the click of a button and with little to no manual intervention. Oh and use Vault. :) Stick with the basics and it will take them a long way.