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 your message to mean you tried a force push and it failed? They
certainly used to work on the ASF repos, but I wouldnt be surprised if
it doesnt any more due to the gitbox+github dual repo setup since
rewriting history will likely cause more issues with that in place, so
it probably hasnt worked since late last year / early this year?

Robbie

On Thu, 22 Aug 2019 at 12:34, Clebert Suconic <[email protected]> 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 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't have a way to push -f?
>
>
> Any ideas?
>
>
>
>
> --
> Clebert Suconic

Reply via email to