git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Reducing Git Repository size - git-filter-repo doesn't help

From
FAfawaz ahmed0 <fawazahmed0@hotmail.com>
Date
Jan 11, 2023, 20:08 UTC
Message-ID
<PH7PR12MB77959E90F52C59140ED662DBF1FC9@PH7PR12MB7795.namprd12.prod.outlook.com>
In-Reply-To
<CABPp-BGh17pH1DUgPOoaDKBcKay3NAyi4js-HnEKAAyYUBSoYQ@mail.gmail.com>
Thank you for looking into this.

I have removed all the unnecessary refs on remote, and rerun the filter-repo and force pushed the changes again. To be be sure, I have also requested Github support to completely nuke the refs/pull and clear cache etc.

Also would like to let you know that git-filter-repo --analyze (which was also suggested by EriK), causes OOM in my case (also tried running in github actions with huge swap, but it exceeds 6 hours timeout limit).

I have verified size reduction (after running filter-repo) using: `git gc && git count-objects -vH`

Thank you once again for the help
Previous: Elijah NewrenNext: fawaz ahmed0
Message 9 of 11 in “Reducing Git Repository size - git-filter-repo doesn't help”
  1. fawaz ahmed0Jan 9, 2023
  2. rsbecker@nexbridge.comJan 9, 2023
  3. fawaz ahmed0Jan 9, 2023
  4. Erik Cervin EdinJan 9, 2023
  5. Elijah NewrenJan 10, 2023
  6. fawaz ahmed0Jan 10, 2023
  7. Elijah NewrenJan 11, 2023
  8. Elijah NewrenJan 11, 2023
  9. fawaz ahmed0Jan 11, 2023
  10. fawaz ahmed0Jan 12, 2023
  11. Elijah NewrenJan 12, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.