whotracksme / whotracks.me

Data from the largest and longest measurement of online tracking.
https://www.ghostery.com/whotracksme
MIT License
407 stars 73 forks source link

Remove all traces of "git lfs". #255

Closed philipp-classen closed 2 years ago

philipp-classen commented 2 years ago

Note: Even if we migrated away, if you have git-lfs installed, it will still attempt to run git lfs after cloning. That results in an error (quota exceeded):

git clone https://github.com/whotracksme/whotracks.me.git
...
Error downloading object: static/img/blog/autoconsent/cookie-blocker-after.gif (ddba742): Smudge error: Error downloading static/img/blog/autoconsent/cookie-blocker-after.gif (ddba742eb728b4cd59fbd5b1ca7f136f68b9d5f298511cc96e238275f0c545da): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Errors logged to /whotracks.me/.git/lfs/logs/20211130T165929.516695513.log
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: static/img/blog/autoconsent/cookie-blocker-after.gif: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'
philipp-classen commented 2 years ago

@y3ti I assume after that change, Jenkins could also drop the git lfs support:

https://github.com/whotracksme/whotracks.me/blob/b3ef5501b2d99d3f16a5b267c9b42d3e936aa421/Jenkinsfile#L13

chrmod commented 2 years ago

wonder if we should rewrite git history to remove the big files

y3ti commented 2 years ago

I think we will need to contact GitHub Support.:

If you need to purge a removed object and you are unable to delete the repository, please contact support for help. https://docs.github.com/en/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage