You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed this repository takes a little white to clone whenever I am setting up a new project. I suspect it's probably due to the example gifs (and/or versions of these or other large files in the repo history). Is there anything that can be done to reduce the repository size for an unmodified git clone operation? I suspect there is probably a way to download the repository without history given some switch on clone, which would also help, but I wonder if there's something that can be done to "archive" this history or maybe move the gifs to a non-master branch?
The text was updated successfully, but these errors were encountered:
For reference it just took about 35 seconds to clone. Also the folder currently takes about 700MB on disk (354MB for the .git folder and 339MB from the "test/in" folder)
That's the testing/benchmarking data. The idea was for contributors to be able to pull down the repo and use the same setup that I use to test their changes, while normal users just download the header file from the repo or from the latest release. If you have a workflow that requires cloning the repo (for example as an automated build step), let me know and I'll look at moving the test setup to a separate repo and scrubbing it from the history.
I've noticed this repository takes a little white to clone whenever I am setting up a new project. I suspect it's probably due to the example gifs (and/or versions of these or other large files in the repo history). Is there anything that can be done to reduce the repository size for an unmodified git clone operation? I suspect there is probably a way to download the repository without history given some switch on clone, which would also help, but I wonder if there's something that can be done to "archive" this history or maybe move the gifs to a non-master branch?
The text was updated successfully, but these errors were encountered: