On Wed, Jan 15, 2014 at 8:08 AM, Andrea Aime
<[email protected]>wrote:
> On Wed, Jan 15, 2014 at 3:51 PM, Ian Schneider <
> [email protected]> wrote:
>
>> More troublesome - other branches have been reset to earlier state.
>>
>> Check out:
>> https://api.github.com/repos/geoserver/geoserver/events
>>
>
> Ah, very useful for forensics... it seems Alessio did a push --force, or
> something like that...
> there are many of those
>
Right, force push will do that.
>
>
>>
>> And look at 1944681713 (the first one when I looked)
>>
>> I would guess that event 1944681630 was the culprit and resetting master
>> HEAD to 633fa54f0dc5ef441d120fead6a61066c4bbf444 might work - but I haven't
>> dug much more than this.
>>
>
> Do you know of any way to revert those events?
> I can reset master to that commit and then... do a push --force again?
>
Correct but for each branch.
github enterprise allows preventing force pushes but the rest of use just
have to be careful :)
--
Ian Schneider
Software Engineer | Boundless
[email protected]
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
