Open patrickcgray opened 4 years ago
Yes, I agree. One approach is to only 'clear all output' before committing to the repository, for any programs you are collaborating on. This generally makes it easier to work together when using notebooks.
There are two (1, 2) options for pre-commit hooks that make sure the output is stripped before notebooks are committed.
@ocefpaf has a selection of pre-commit hooks here for IOOS projects, that might be good starting point if you wanted to add hooks to your project to get code on the same page and help prevent conflicts.
After battling git to merge all my jupyter notebook changes we should implement a process for better managing .ipynb files on git if we're going to keep using them. I know there are a couple good tools for this, https://nbdime.readthedocs.io/en/latest/ seems promising without inflicting too much overhead on normal procedures. I'm not familiar with many of them if others have suggestions!