This repository has been archived by the owner on Aug 19, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 132
Making the git extension a generic Jupyter extension? #78
Comments
I would love this one too .... |
+1 for me, this would be very useful. |
I'd like to put my vote in for this too. It'd be a great feature! |
Another +1 |
+100 Been looking for this too |
+1, It can be a part of the essential notebook workflow. |
+1, useful |
+1 |
+1 I would love to see this |
Hi all, I have tried and successfully implemented this as a jupyter extension. |
Great! I would love to install the extension. How does one go about doing that? @sat28 |
@sebratt I have elaborated the details inside the readme. Please feel to post any issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Whilst looking for a Jupyter notebook extension that would link a notebook checkbook to git commit and allow checkpoint recovery from git pushes, I came across your bespoke Commit-and-Push to GitHub from Jupyter Notebooks extension.
(In passing, I also found a GitCheckpoints package, though I haven't had a chance to try it/see if it works with Jupyter.)
I seem to recall from some of the Jupyter Google group discussions that elaborate checkpointing schemes were unlikely to become part of the core offering, so the extension way seems to be the way to go.
FWIW, SageMathCloud also has some interesting backup and history replay features, so you can replay the history of a notebook. The granularity of that seems finer grained than the git commit route is likely to offer, but it does demonstrate one way of replaying histories.
Another piece of the jigsaw when it comes to making use of commits is to have an environment for comparing diffs. With github supporting nbviewer displays of notebooks, I wonder if they are also contributing to work on an nbdiff-er. (nbdiff seems to have stalled, for example)? The csiro-scientific-computing folk who did the GitCheckpoints routine also seem to have explored diffs: NotebookDiff.
The text was updated successfully, but these errors were encountered: