clean up repo

[Remi-Gau]

not very urgent but this repo is getting kind of big and this may come back to bite us if we need to do any operation on it at some point

suggestion : squash commits in between release and purge the history

[Remi-Gau]

@ymzayek @bthirion

[ymzayek]

Agreed

[bthirion]

Sorry, but what is the risk ?

[Remi-Gau]

not very high except that some operations that should be fast (clone, fetch) are very slow on the repo already and they may get to a point where they are so slow they prevent us from working on it

[AlexandreAbraham]

Whether you clean it or not, do not hesitate to use partial clone. Blobless and treeless clones can save you juge amounts of time. Basically, these clones download part of the history but not all the diffs. Those diffs are accessed only when needed.

[Remi-Gau]

I agree but that's when you need to those diffs that things may get sluggish. So it is definitely just a once in a blue moon use case (only discovered it when wanting to check what a page of the doc looked like in previous versions) but for long term maintenance it may be better.

[Remi-Gau]

yeah cloning the repo on a slow connection is quite sluggish

what is the risk ?

not being able to clone the repo sounds quite risky