[stochastician]

Many existing version control tools help with this, but there are some challenges that crop up when doing this with jupyter notebooks:

1. Versioning notebooks in a semantically-useful way is difficult: think of it more like versioning binary data than source code. I know we struggle with this a fair amount.

2. There are many debates, some here on HN, about "best practices" for collaborative versioning (do you squash? rebase? etc). These questions exist for notebook users too, and there's a lot of interest in developing tools that either make these decisions for you (are opinionated), integrate them more into the GUI nature of notebooks, or both.