From: fawaz ahmed0 <fawazahmed0@hotmail.com>
To: Elijah Newren <newren@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"rsbecker@nexbridge.com" <rsbecker@nexbridge.com>
Subject: Re: Reducing Git Repository size - git-filter-repo doesn't help
Date: Tue, 10 Jan 2023 08:18:51 +0000 [thread overview]
Message-ID: <PH7PR12MB7795ED45E989E2EDE2364049F1FF9@PH7PR12MB7795.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CABPp-BE_FLFL3-s3936zWWfaORBPim14A-oqVNo+8gx+CMduHA@mail.gmail.com>
> Note that git-filter-repo only changes the size of the _local_ repo.
You made an additional clone within GitHub Actions, and then
filter-repo shrinks *that* clone. Even if you had deleted all copies
of older files you don't want anymore locally (which is suspect as I
noted above), your force pushing isn't going to shrink the size of the
repo on the server (i.e. on GitHub) since there are pull requests in
your repo that GitHub won't allow you to overwrite via force-push, and
those pull requests still hold on to the old history.
Thanks for your inputs. Yes, the issue is with the GitHub itself (I have verified it locally), so when I force push this reduced sized repo to Github and reclone it back the size gets back to 4+ GB.
So what do you suggest?
I have already contacted Github few days back, and they have cleared the cache etc for this repo.(but that did not reduce any size). ( I will try contacting them again)
> Why are you cleaning up in a CI task?
Task is yearly cleanup, to keep repo under 5GB limit as recommened by Github ( To avoid receiving email from GitHub : https://github.com/whosonfirst-data/whosonfirst-data/issues/1507 )
> Could you provide that number and how you got it, so we can see what you're measuring
I was checking the repo size here: https://github.com/settings/repositories (it takes around 1 hour for github to show updated size after any commit)
next prev parent reply other threads:[~2023-01-10 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 2:22 Reducing Git Repository size - git-filter-repo doesn't help fawaz ahmed0
2023-01-09 2:36 ` rsbecker
2023-01-09 3:29 ` fawaz ahmed0
2023-01-09 10:22 ` Erik Cervin Edin
2023-01-10 2:42 ` Elijah Newren
2023-01-10 8:18 ` fawaz ahmed0 [this message]
2023-01-11 2:18 ` Elijah Newren
2023-01-11 8:41 ` Elijah Newren
2023-01-11 20:08 ` fawaz ahmed0
2023-01-12 1:54 ` fawaz ahmed0
2023-01-12 2:01 ` Elijah Newren
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PH7PR12MB7795ED45E989E2EDE2364049F1FF9@PH7PR12MB7795.namprd12.prod.outlook.com \
--to=fawazahmed0@hotmail.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=rsbecker@nexbridge.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).