I also thought that we have disabled force push on master and other release
branches but I tried and succeeded... There are 20+ commits and it is only
a few seconds after the accidental push so I just used a force push to
revert everything back...
2018-05-15 21:32 GMT+08:00 Sean Busbey :
> In the
FYI for those interested I filed INFRA-16532
On Tue, May 15, 2018 at 8:32 AM, Sean Busbey wrote:
> In the future please don't do force pushes. I thought we had disabled
> them for the master branch. I'll check up with Infra on this.
>
> Next time just push a revert.
>
> On Tue, May 15, 2018 at 8:
In the future please don't do force pushes. I thought we had disabled
them for the master branch. I'll check up with Infra on this.
Next time just push a revert.
On Tue, May 15, 2018 at 8:11 AM, 张铎(Duo Zhang) wrote:
> Thanks.
>
> I pushed HBASE-20457 to master and then the Github repo is back to
Thanks.
I pushed HBASE-20457 to master and then the Github repo is back to normal...
2018-05-15 19:10 GMT+08:00 Tim Robertson :
> Perhaps someone can verify this first:
>
> // assuming you have ASF upstream of GH (git remote add upstream
> git fetch upstream
> git checkout master
> git reset --
Perhaps someone can verify this first:
// assuming you have ASF upstream of GH (git remote add upstream
git fetch upstream
git checkout master
git reset --hard upstream/master
git push origin master --force
This should force (i.e. destructive operation) the GH master branch to be
the same as th
When committing HBASE-20576...
I've done a force push to master immediately and the asf git is back to
normal, but the github repo has already been messed up.
Does anyone know how to get the github repo back?
Really sorry about this...
