-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clean cell outputs at merge time #3
Labels
Feature Request
A new feature that's under consideration.
Comments
amit1rrr
changed the title
Remove cell outputs at merge time
Clean cell outputs at merge time
Oct 27, 2018
Would be an awesome feature. FWIW Base on my workflow I'd make heavy use of the:
I'd make much less use of the option to select specific cells to keep. If that helps make the scope easier |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
Lot of users want to version control only the source (markdown + code cells) but don't wish to commit output into their git repository. They currently do this via nbstripout or with "Clear All Outputs" in the Jupyter UI.
The problem is, sometimes you might want to keep an output for some notebooks or even for some cells in the Notebook. Then both the earlier options are kind of icky. Also, people sometimes just tend to forget to hit "Clear All Outputs" before committing.
Solution
We can give users ability to clean output at merge time. They can view the entire diff and select which outputs they want to keep (if any) and once the review is complete and user hits merge we can remove the output and push a new commit with the stripped version.
Moreover, we can let user configure the repo to always strip all output at every merge so no more forgetting to clean output. If you need to overwrite the stripping for a few select cells, just mark those in the merge UI and we'll keep those outputs and clean everything else.
Benefits
Feel free to upvote/downvote the issue indicating whether you think this is useful feature or not. I also welcome additional questions/comments/discussion on the issue.
The text was updated successfully, but these errors were encountered: