Remove large refs from git #3

New Issue

shaunrd0 · 2022-09-10T14:11:46Z

shaunrd0 commented

2022-09-10 14:11:46 +00:00

The models are large and slow down clones. Removing them won't help because git will continue to track these large refs.

Will probably have to rewrite history to remove these refs. Simple geometry like cubes and triangles could be built and scaled to size using C++ in both 2D and 3D.

Could possibly use a LFS submodule sourced from git.shaunreed that can optionally be initialized for additional objects.

The models are large and slow down clones. Removing them won't help because git will continue to track these large refs. Will probably have to rewrite history to remove these refs. Simple geometry like cubes and triangles could be built and scaled to size using C++ in both 2D and 3D. Could possibly use a LFS submodule sourced from git.shaunreed that can optionally be initialized for additional objects.

shaunrd0 added the

bug

label 2022-09-10 14:11:46 +00:00

shaunrd0 commented

2025-04-12 16:19:52 +00:00

#16 partially addressed this but only by removing them from the application. The references still exist in git, I'd like to remove them but not at risk of losing history. I'd imagine removing these references in git would mean that checking out earlier versions of the repository would not work correctly since git wouldn't have references to checkout the files.

This probably means the repository will be archived and migrated to a new repo. That's ok with me honestly, I've been considering renaming anyhow and I'd like to detach myself from GitHub's CI runners entirely. We could always reference this repo for digging through the oldest history.

#16 partially addressed this but only by removing them from the application. The references still exist in git, I'd like to remove them but not at risk of losing history. I'd imagine removing these references in git would mean that checking out earlier versions of the repository would not work correctly since git wouldn't have references to checkout the files. This probably means the repository will be archived and migrated to a new repo. That's ok with me honestly, I've been considering renaming anyhow and I'd like to detach myself from GitHub's CI runners entirely. We could always reference this repo for digging through the oldest history.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: shaunrd0/qtk#3