> Master should always be in a deployable state. +1 to this and squashing commits. I'd even go far as saying trunk based deployment model over trunk based deve

> Master should always be in a deployable state. +1 to this and squashing commits. I'd even go far as saying trunk based deployment model over trunk based development. This can be done via Pull requests or short lived branches. I prefer having all the context, discussions and testing added to the pull request. Even setting up environment per pull request. It's much easier to track and get feedback.