Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rewrite git history to remove jupyter notebook outputs #59

Open
bkmi opened this issue Aug 2, 2021 · 1 comment
Open

rewrite git history to remove jupyter notebook outputs #59

bkmi opened this issue Aug 2, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@bkmi
Copy link
Collaborator

bkmi commented Aug 2, 2021

Our repo is needlessly large because of the excessive saves of notebooks from previous git commits. This can be undone. We should do so.

A method can be found here:
https://mg.readthedocs.io/git-jupyter.html#cleaning-a-whole-repository

@cweniger are you fine with this? If you want to save the output of the current notebooks we can keep them in the next version release.

In general, we should avoid changing the notebook outputs if possible. One option would be to clear them automatically with pre-commit.

@bkmi bkmi added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Aug 2, 2021
@bkmi bkmi assigned cweniger and bkmi Aug 2, 2021
@bkmi
Copy link
Collaborator Author

bkmi commented Nov 22, 2021

The suggestion on that site is to leave the master with executed notebooks and have a dev branch without.

imo swyft should download instantly and right now it takes some time because of all of this notebook bloat. Is it worth deleting it all? I think yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants