this repository is very, very big...

[ctb]

...should we really be storing GFF3 flat files in it?

[ctb]

looks like maybe it's mostly the git history that's large. We could consider squashing the history.

[ACharbonneau]

relic from before we moved all the big files to OSF. If the history can be downsized that'd be neat

[ctb]

thx @ACharbonneau -

@abradyIGS could you provide guidance on where would be a good place in the commit history to reset the repo to? date, or specific commit - whatever. preferably someplace after where all the big files were removed :)

[abradyIGS]

I keep my own local mirrors of all the important versions of things, or at least the ones I care about -- so I don't rely on git history for retrieval and therefore don't have an opinion. Deleting history data prior to [anywhere you like that fixes the space issue] is fine with me.

[ctb]

while I appreciate your concern for my concern, that was not my concern 😆 .

when did you move all the big files to OSF, roughly? or do I need to dig through history to find out?

[ACharbonneau]

OSF got big files in August of 2021. Unsure when they would have been deleted here, but presumably around then. I would pick a commit in september or october 2021 and it will likely work

[ACharbonneau]

oh. Uh. So. It looks like the big files were moved to OSF but not actually removed from here...

[abradyIGS]

i should do that, then. looks like our history cutoff will be quite current

[abradyIGS]

argh, it's the developer tools section, i see it now. it's got copies of the big C2M2 CV reference files because it contains the code that generates those big reference files from their respective batches of raw source data. we moved the (generated, finished) reference files to OSF, but i didn't migrate this section: i'll need to do that. gimme a day or two

[abradyIGS]

(i am also going to try to replace some of these big source files with pointers to their third-party locations, so the migrated OSF node should be smaller than what's here on git now)