The deploy happens asynchronously from the push. Instead of having a separate repo you push to in order to deploy, the main branch of the shared GitHub (or whatever) repo just gets automatically deployed whenever there's a push (or sometimes it's triggered by a tag). So there's no feedback at all on push.
Ah of course! In fact I even have one personal project with collaborators, and indeed I've set it to deploy on push using GitHub actions, and indeed there's no feedback.
Pushing straight to the prod server is nicer UX, but I guess that only works reasonably well with one person, or a very tiny team.
