> 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)
