Investigate ways to reduce Git repo sizes
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
Menu
▾
▴
#29 Investigate ways to reduce Git repo sizes
Cloning the tuxpaint-website repo can take a very long time. It contains many years of history, which includes huge amounts of image data from the original and new galleries, which have since been moved to the tuxpaint-website-gallery repo. However, the history of those files remain in the repo, making it tedious to clone.
Will Thompson suggests that people interested in cloning a repo could potentially use a "shallow clone, to just fetch the latest revision", but is unsure how that might interact with merge requests to the upstream (this project's) repo. Other options include rewriting history, and/or starting a new repo. There appear to be many different kinds of solutions when searching Google. We'll need to put some careful thought into this.
Perhaps an orphan branch, per "Alterntative 1" in this Stackoverflow post...? https://stackoverflow.com/a/24154149