Skip to content

Announcement: Users Will Need To Re-clone Repo Soon #263

Description

@DarnellGranberry

Hi all,

At one point during Topaz development, I uploaded a small dataset of micrographs to Topaz's Git LFS bucket. Even after removing them from the repo, they still count against Tristan's upload/download quota each time someone clones the repo. The only way for us to remove them involves rewriting the entire repo history; you can read more about the side effects of this here. Primarily affected will be those who have cloned the repo, who will have to re-clone it (instead of git pull-ing) to update, and those with open pull requests.

We do not currently have a hard timeline for when this will happen, but hope to implement it soon. We're posting this as a heads-up for current users, and as documentation in case anyone encounters related issues in the future.

As always, please let us know if you encounter any errors or other issues.

Metadata

Metadata

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions