Skip to content

Git history is getting huge due to Jupyter Notebooks #129

Description

@timtreis

Just cloned the repo and noticed that it was taking quite some time, downloading 550 MB for a fairly low-LOC repo:
image

I wonder if there's any merit towards switching to a fork/squash-merge approach instead of the branch based? Realistically, that history is only ever going to become larger.

Counterpoint:

  • This repo is not really something many people outside devs clone so it might be overengineering.

wdyt @giovp @LucaMarconato ?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions