The publication is the merge
A site that publishes on a push is a site with no review: whoever writes is not whoever puts it live.
- process
- review
- deploy
Every project has a button that publishes. Here the button belongs to someone else: the text arrives as a review request, the review becomes a merge, and the merge is the publication. No local command puts anything live.
It looks like ceremony for a site that is only Markdown. It looks like that right up, say, to the second time today's hurry has to undo yesterday's text: then the review that felt slow is the only thing between "I thought it was fine" and "it is live and I already showed it to someone".
Automatic deploy is not the problem. Automatic deploy with no gate is: when publishing costs one push, reviewing has to cost at least one gate.