Emacs org mode definitely got this right. Storing everything as json feels like an ok choice, but there is a huge advantage to storing in the repo exactly what you review.
There is also another tool called `pynb` (by the same author) that can be used to achieve human-readable format. The logic is a bit different there, since it generates a .py script file with markdown cells appearing as Python comments.
Hi Ivan, author here. Happy to read that pynb is useful! it can be used in a similar way (I used it also this way until I required support also for Zeppelin), however, it's limited to Jupyter and there's no Markdown support as you already pointed out.
10 comments
[ 2.7 ms ] story [ 34.6 ms ] threadexample diff: https://github.com/minireference/noBSLAnotebooks/commit/9005...
script: https://github.com/minireference/noBSLAnotebooks/blob/master...
pre-commit hook: https://github.com/minireference/noBSLAnotebooks/blob/master...
GitHub: https://github.com/iodide-project/iodide
Post explaining what it is: https://hacks.mozilla.org/2019/03/iodide-an-experimental-too...
It uses this markdown like file format: https://iodide-project.github.io/docs/jsmd/
At least then you're dealing with diffs of plain text instead of json.
I built ReviewNB (https://www.reviewnb.com/) specifically to review Jupyter Notebooks on GitHub.