Many teams - why, I don't know - dislike automated deployments, but do like being able to trigger a deployment without needing to setup local deploy environments. In this case, having a bot is useful.
In a way, my setup doesn't automate deployments - i.e. you never inadvertently deploy by committing some code or merging a PR (when your intent was merely approving some code).
That's why I made the master vs. master-xxx distinction: deployments are an explicit action, which you are free to defer as needed.
That's why I made the master vs. master-xxx distinction: deployments are an explicit action, which you are free to defer as needed.