repository size grew to 400mb (!)

[fzimmermann89]

git clone takes now a considerable time and disk space.

For example, in he intern_backup branch, there are h5 files.

these will be copied on every single clone.

we should remove the big binaris from the history. not sure when and if github run git gc, i.e. if the space will be free'd if we remove the offending branches or if we would have to do some other steps to clean up.

for the future, we should really avoid doing that! instead, people should consider using local branches if they want to commit binary files to github, or save them somewhere on echo. this is something we should tell new collaborators if we continue to use one writable shared repo.

[fzimmermann89]

almost 400MB!!!

this makes it inaccessible if you don't have a fast internet connection. and most of the space is wasted. there is no inherent need for this much space!

also, we might consider git lfs for storing the example notebooks. we might also consider moving the example notebooks to a different repo, link it in our readme, place a readme.md in examples. Would it be possible to deploy the notebooks to a different repo than this one? @ckolbPTB

[ckolbPTB]

I have removed the culprit branch so hopefully github garbage collection will soon remove it completely, otherwise we have to do it ourselves.

In the main time adding "--single-branch" to git clone will restrict the clone to the main branch.

The problem here was indeed a wrong commit containing raw data files. The notebooks should not be a problem because they only contain text and no content.

[fzimmermann89]

Ah, perfect. I forgot that we do not save images in the notebooks. Let's see if GitHub ever does a garbage collection (according to stack overflow, maybe not - we would have to open a support ticket 🙈)