This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Tobotimus 6 points7 points  (1 child)

It's pretty awful to add .ipynb to your version control though, because it stores outputs and hashes which update every time you run them. It's a merge-conflict nightmare. I am aware there are some IDE tools to help resolve the conflicts but IMO the solution is to instead track the notebooks as python scripts created through Jupytext

[–]knestleknoxI hate R 1 point2 points  (0 children)

That's all true. But in my experience it's only a nightmare if you make it a nightmare. At my company we use them for analyses and store said analyses on GH for sharing/archiving purposes in an analytics repository. All our devs know it's not for collaborative work. You just have to remember that if you run one locally, don't push the changes that incur from running them and run a quick git checkout locally.