Was there some force push to Roassal?
Hi, Since there is no release for roassal I have projects referencing a SHA of a stable Roassal 2 version. I see in my projects that the roassal SHA targeted was c1da8614c951008ea501f126ef3ccf25d73580ac but now I cannot find it in the history of roassal and my projects are failing. So I am wondering if someone forced pushed on Roassal 2? And if yes, what is the reason? Because of this, all the released of the projects depending on this version of roassal will never work again. Please, please, do not use destructive operations on projects that are intended to be used :( -- Cyril Ferlicot https://ferlicot.fr
Hi Cyril, I tried something to remove some large blob from the history. The code source of Roassal2 is about 7Mb large, but the .git folder is about 150 Mb! But at the end, it was the push was rejected because some pullrequests exist. So, I did not suspect that I had an impact. Sorry about that. Help is welcome to shrink Roassal2âs .git folder. Cheers, Alexandre
On 07-11-2019, at 19:33, Cyril Ferlicot D. <cyril.ferlicot@gmail.com> wrote:
Hi,
Since there is no release for roassal I have projects referencing a SHA of a stable Roassal 2 version.
I see in my projects that the roassal SHA targeted was c1da8614c951008ea501f126ef3ccf25d73580ac but now I cannot find it in the history of roassal and my projects are failing.
So I am wondering if someone forced pushed on Roassal 2? And if yes, what is the reason?
Because of this, all the released of the projects depending on this version of roassal will never work again.
Please, please, do not use destructive operations on projects that are intended to be used :(
-- Cyril Ferlicot https://ferlicot.fr
participants (2)
-
Alexandre Bergel -
Cyril Ferlicot D.