You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jupyter Notebooks are great for documentation, however, reviewing code in notebooks is a pain and often requires reviewing changes locally.
Since the rdtools documentation is written mainly in notebooks I think it's worth considering using the ReviewNB GitHub app. ReviewNB integrates into the GitHub PR discussion flow and gives the option to view the new and old versions of the notebook side by side with changes highlighted. It is possible to add comments to specific notebook cells, which then show up in the PR discussion.
It's free for open-source projects and very easy to get started with, so if anything I would recommend trying it out for a short period to see if it adds value to the project.
You can check out an example PR with a single review here, where the interface looks like this:
The text was updated successfully, but these errors were encountered:
Note that this is different from, and maybe complementary to, #270. This is for diffing notebook content whereas #270 is for checking that the new notebook runs correctly.
Jupyter Notebooks are great for documentation, however, reviewing code in notebooks is a pain and often requires reviewing changes locally.
Since the rdtools documentation is written mainly in notebooks I think it's worth considering using the ReviewNB GitHub app. ReviewNB integrates into the GitHub PR discussion flow and gives the option to view the new and old versions of the notebook side by side with changes highlighted. It is possible to add comments to specific notebook cells, which then show up in the PR discussion.
It's free for open-source projects and very easy to get started with, so if anything I would recommend trying it out for a short period to see if it adds value to the project.
You can check out an example PR with a single review here, where the interface looks like this:
The text was updated successfully, but these errors were encountered: