If you are behind git warns you and says you need to pull first. By stating -f you are saying nope, throw that crap away and just take my version.
That's pretty extreme and warrants care. I have a hard time feeling sorry for people who are burned by this.
I also just like pushing to a branch on Github, even if I might rebase later. Circle CI is triggered through Github, so it's nice to have that triggered for me. Our staging servers (production data, your branch's code) are deployed from Github branches as well. Plus looking at diffs on Github is really helpful for me to spot errors—I'm not sure if it's the context switch away from my text editor, Github's diff UI, or what, but it works for me.
And that's also unreasonable. Pushed history should be treated as immutable. If you broke the build, push a revert commit, fix the issue, and resubmit. And then fix your tooling to recognize rollbacks.
git push -f
* I made a topic branch and push it for review on github
* I immediately found a trivial typo in my code
* I amended my commit to fix the typo
* I did push -f to overwrite the topic branch on
* OOPS. I pushed all my branches. >.<
It doesn't seem peculiar at all, to me.