We periodically prune old builds from our TUF repo server. This means that we probably are left with some treehub objects that are no longer referenced. ie - if delete target "foo" with hash 0xdeadbeef, then 0xdeadbeef could be removed from treehub. And removing that means that some of its references could be removed. kind of what git-gc does. Does treehub anything like this to help control the size of its object database/store?
We periodically prune old builds from our TUF repo server. This means that we probably are left with some treehub objects that are no longer referenced. ie - if delete target "foo" with hash 0xdeadbeef, then 0xdeadbeef could be removed from treehub. And removing that means that some of its references could be removed. kind of what git-gc does. Does treehub anything like this to help control the size of its object database/store?