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
Is your feature request related to a problem? Please describe.
not exactly a feature request, but i noticed the repo is over 1 GB right after cloning, which feels pretty big for a docs project. maybe it comes from large files or old artifacts hanging around in the .git history.
Describe the solution you'd like
i think maybe a history cleanup to get rid of any big or outdated files could be worth it.
Additional context
i checked for large files in the repo history, and here’s what came up:
most of these files aren’t in the main repo anymore, they’re still in .git and adding to the size. the only large file still in use is drawing.svg (20 MB), which is still too big for the web ideally it’d be around 50 or 200KB max.
also, when i checked dir sizes at root, .git alone was already 1 GB 👀
hi @bucanero
just tested out cloning only master branch like suggested, turns out size is only 203.63 MB✅
and not 1 GB. so seems like the repo should be fine as is. thx again for taking the time to look into this!
Is your feature request related to a problem? Please describe.
not exactly a feature request, but i noticed the repo is over 1 GB right after cloning, which feels pretty big for a docs project. maybe it comes from large files or old artifacts hanging around in the .git history.
Describe the solution you'd like
i think maybe a history cleanup to get rid of any big or outdated files could be worth it.
Additional context
i checked for large files in the repo history, and here’s what came up:
most of these files aren’t in the main repo anymore, they’re still in
.git
and adding to the size. the only large file still in use isdrawing.svg
(20 MB), which is still too big for the web ideally it’d be around 50 or 200KB max.also, when i checked dir sizes at root, .git alone was already 1 GB 👀
feel free to dive in further!
The text was updated successfully, but these errors were encountered: