It is also possible to force push "unprotected" branches - most branch names are not given protection, only a few like 'trunk', 'master', etc. - so that's an option. I'm not suggesting we do anything differently, but wanted you to be aware of this.
On Mon, May 11, 2015 at 11:08 AM, Konstantin Boudnik <[email protected]> wrote: > Yup, not big a deal ;) > > Actually, there's a way to force push, but it involves ppl from INFRA and > they > aren't happy with that. So, unless not doing a force push is a disaster - > let's try to avoid it ;) > > Cos > > On Mon, May 11, 2015 at 09:41AM, jay vyas wrote: > > no prob olaf, happens to us all at times. > > > > we can't force push. > > > > just do a manual revert in a jira and we'll commit the reverts ! > > > > On Mon, May 11, 2015 at 2:01 AM, Olaf Flebbe <[email protected]> wrote: > > > > > Hi, > > > > > > While I was in a rush, I accidentely checked in a couple of bogus > > > commits (They were not merged properly) > > > > > > The resulting code is o.k. but commits in between are not. > > > > > > Can we revert origin/master back to > > > f83a9c48af6031015e175326a3a3e25bf749b2f2, the last regular commit ? > > > > > > git checkout origin/master > > > git reset —hard f83a9c48af6031015e175326a3a3e25bf749b2f2 > > > git push -f > > > > > > As a safety measure this is disabled for common committer like me … > > > > > > > > > Greetings, > > > Olaf > > > > > > > > > > > -- > > jay vyas > -- Best regards, - Andy Problems worthy of attack prove their worth by hitting back. - Piet Hein (via Tom White)
