Maybe you should look into deploying GitHub Large File Storage <https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage> (LFS). If applicable, store large documentation files in LFS to reduce the repository size.
HTH Mich Talebzadeh, Architect | Data Engineer | Data Science | Financial Crime PhD <https://en.wikipedia.org/wiki/Doctor_of_Philosophy> Imperial College London <https://en.wikipedia.org/wiki/Imperial_College_London> London, United Kingdom view my Linkedin profile <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> https://en.everybodywiki.com/Mich_Talebzadeh *Disclaimer:* The information provided is correct to the best of my knowledge but of course cannot be guaranteed . It is essential to note that, as with any advice, quote "one test result is worth one-thousand expert opinions (Werner <https://en.wikipedia.org/wiki/Wernher_von_Braun>Von Braun <https://en.wikipedia.org/wiki/Wernher_von_Braun>)". On Thu, 8 Aug 2024 at 22:02, Sean Owen <sro...@gmail.com> wrote: > That seems a liiiitle bit too much to me. I could see people still on a > recent version that just want to see docs or compare/contrast docs for > changes. > Removing the versions that seem to have ~0 traffic would remove, it seems, > like 80% of the .html files (and replace them with a compressed archive > that's smaller), which seems 'enough' for the moment? > > But if docs releases are 1GB going forward, this will be an issue again > soon. > > On Thu, Aug 8, 2024 at 1:25 PM Wenchen Fan <cloud0...@gmail.com> wrote: > >> It makes sense to me to only keep the doc files for the latest >> maintenance release. i.e. remove the docs for 3.5.0 and only keep 3.5.1. >> >>> >>> >>>
