Forbid force-pushing phase changes
Description
I just forced-pushed a phase change because I screwed up my local config and pushed a topic-less draft commit. I was told that this was not a supported use case and that I should feel bad (jk).
Proposal
We should outright refuse force-pushing a phase
I feel like this is a hard requirement as a user, and that it should be better supported by tools:
- We need better logging to warn people that they've just published something and/or merged a MR
- I would love a feature that refused any topic-less push, requiring the public phase change to be an explicit local one.