search

pulibrary / aspace_helpers

methods and reports to support common SC activities in ArchivesSpace
1 stars 0 forks source link

Investigate Git LFS usage #525

Closed maxkadel closed 2 months ago

maxkadel commented 2 months ago

It appears Github thinks we are still using its LFS - see https://github.com/organizations/pulibrary/settings/billing/summary image

At one point we investigated using LFS as an alternative for keeping EAD snapshots (around Spring 2022), but ultimately decided against it.

We should determine why Github billing still thinks we are storing LFS with them, and find a way to delete it, so we are not accidentally billed in future.

What we've tried

git lfs ls-files
# no return
➜  aspace_helpers git:(main) git lfs migrate info
migrate: Fetching remote refs: ..., done.
migrate: Sorting commits: ..., done.
migrate: Examining commits: 100% (0/0), done.

Implementation notes

See https://docs.github.com/en/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage#git-lfs-objects-in-your-repository - do we really have to delete the whole repo to not be charged for storage?

regineheberlein commented 2 months ago

I've contacted Github about this

maxkadel commented 2 months ago

@rlskoeser has had a good experience with contacting GitHub support for this in the past.

regineheberlein commented 2 months ago

The LFS objects have been deleted by Github support. They still recommend following the steps described here to remove them from the history. I'll look into that.