Clear output on commit #2
Open
+430
−16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
euanmillar
force-pushed
the
clear-output-on-commit
branch
from
4b587e2 to
2cd59f9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed that you have to click "Clear All Outputs" in VSCode before doing a commit otherwise the git diff clogs up with your logs. I read that configuring
nbstripoutis the way to clean output on git commits in Jupyter. My version of Jupyter uses incremental numbers rather than hashes to define cell ids in metadata. ChatGPT claims that newer versions of Jupyter do this. Perhaps there are benefits. The rest of the diff looks clean after these changes but installation steps are slightly more complex.