Large repo size: unwanted .pack files
See original GitHub issueCurrent Behavior
The layer5
repo is over 2GB in size due to unwanted .pack files in .git/objects/pack
.
Desired Situation A smaller repo size.
Contributor Resources
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master
branch.
- See contributing instructions
- See Layer5 site designs in this Figma project. Join the Layer5 Community for access.
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (12 by maintainers)
Top Results From Across the Web
Consider cleaning up the .git folder to reduce the large repo size
The next step would be to clean up your git by removing all of those unnecessary files. One option is to use the...
Read more >Trying to reduce my repository size by reducing PACK file
The Pack file in my repo is so bit like 10.8GB us showing kindly suggest me best way to reduce the size of...
Read more >Remove large .pack file created by git - Stack Overflow
Scenario A solved mine problem, to delete a big amount of temporary pack file. The repository was managed by a build server and...
Read more >How to clean up the git repo and reduce its disk size - Git Better
Clean large git repo and reduce repo size. ... This will help you to reduce the size of the pack file itself. git...
Read more >Removing large files from Git without losing history
The simplest method of removing files uses git filter-branch . This command enables you to eliminate particular files from your history. This ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
All yours @Abhijay007
This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.