I don't like push -f, I only use it rarely. I would have used it on
this case as the commit was never meant to be pushed... but it's ok..
we can live with it.
At least I didn't use any curse this time on my commit message...
lol... and no funny debug messages :P
Thanks God is Almost Friday.
Than
I would not do a push -f, just commit a fix on top. With mirrors in
play it may cause problems.
On Thu, 22 Aug 2019 at 12:34, Clebert Suconic wrote:
>
> I did a mistake yesterday, and I pushed a commit I wasn't supposed to.
>
> It was a commit only intended to my box, it says "fix"
>
> nothing to
Force pushing on shared branches, especially across a larger period of
time, is frowned upon because it will often cause other people issues
when they go to pull/rebase etc. If the original change was yesterday,
I'd just use a revert commit regardless whether a force push was an
option.
I read you
I did a mistake yesterday, and I pushed a commit I wasn't supposed to.
It was a commit only intended to my box, it says "fix"
nothing too wrong with it, but it has some checkstyle errors. which I
can fix with a later commit.
but if I could push -f and remove it it would be better.
So, we don'
