jupyterlab-gitplus
SemanticDiff
jupyterlab-gitplus | SemanticDiff | |
---|---|---|
7 | 13 | |
110 | 39 | |
0.0% | - | |
1.2 | 3.2 | |
about 1 year ago | 21 days ago | |
TypeScript | ||
GNU Affero General Public License v3.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jupyterlab-gitplus
-
Difftastic, a structural diff tool that understands syntax
If you are in need of a diff tool for jupter notebooks use https://www.reviewnb.com/ and for word documents use https://www.simuldocs.com/
-
The Jupyter+Git problem is now solved
- GitHub PR code reviews with ReviewNB[4]
Alternatively, if you don't care about cell outputs then Jupytext[5]
Disclaimer: I built ReviewNB. It's a completely bootstrapped business, 5 years in the making and now used by leading DS teams at Meta, AWS, NASA JPL, AirBnB, Lyft, Affirm, AMD, Microsoft & more (https://www.reviewnb.com/#customers)
[1] https://github.com/jupyterlab/jupyterlab-git
-
While you wait for GitHub to finish building Jupyter Notebook reviews
Already a GitHub plugin that does this very nicely: ReviewNB
- Rich Jupyter Notebook Diffs on GitHub... Finally.
-
[Noob question] Why are notebooks not used in production ?
For version control: https://www.reviewnb.com/ helps. Agree with the rest but some experimental notebooks are useful to track/version control.
-
Nbdev: Create delightful software with Jupyter Notebooks
It's not focused on collaboration, but it does add some critical pieces that otherwise make Jupyter development frustrating when working with a team. Specifically: `nbdev_prepare` ensures that diffs are as small as possible, by removing and standardising notebook metadata; and `nbdev_fix` fixes merge conflicts so that they are cell-level, rather than line level, so they can be opened and fixed in notebooks.
Something else we've found helpful for collaboration (not associated - just happy users) is this: https://www.reviewnb.com/ . It means we can get a nice notebook-based PR workflow.
Real-time collaboration is available in Jupyter nowadays: https://jupyterlab.readthedocs.io/en/stable/user/rtc.html . nbdev doesn't have any extra functionality for it, however -- but it should work fine in this environment.
- Ask HN: Are there any good Diff tools for Jupyter Notebooks?
SemanticDiff
-
Difftastic, a structural diff tool that understands syntax
Semantic Diff is probably the closest for now, although I don't think it uses tree-sitter.
https://semanticdiff.com/
Found via https://github.com/Wilfred/difftastic/issues/194.
-
My programming language aware diff for VS Code and GitHub now supports Rust
I am working on SemanticDiff, a programming language aware diff that hides style-only changes, detects moved code and refactorings. I just added support for Rust and would like to know what you think!
-
Prettier $20k Bounty was Claimed
If you're looking for a VS Code extension or a GitHub app, check out https://semanticdiff.com/. I'm a co-founder of this project.
If you prefer a CLI tool, check out https://github.com/Wilfred/difftastic. It supports more languages, but doesn't recognize when code has been replaced by an equivalent version ("invariances"). So it will show some changes (e.g. replacing a character in a string with an escape sequence) even though they are technically equivalent.
-
Large pull requests slow down development
There are some tools that can separate actual code changes from reformatting changes. I am working on https://semanticdiff.com, a VS Code Extension / GitHub App that can help you with this. There is also difftastic if you prefer a CLI based solution. It supports more languages but can detect fewer types of reformatting changes.
-
Pijul: Version-Control Post-Git • Goto 2023
I'm not familiar with Pijul, and haven't finished watching this presentation, but IME the problems with modern version control tools is that they still rely on comparing lines of plain text, something we've been doing for decades. Merge conflicts are an issue because our tools are agnostic about the actual content they're tracking.
Instead, the tools should be smarter and work on the level of functions, classes, packages, sentences, paragraphs, or whatever primitive makes sense for the project and file that is being changed. In the case of code bases, they need to be aware of the language and the AST of the program. For binary files, they need to be aware of the file format and its binary structure. This would allow them to show actually meaningful diffs, and minimize the chances of conflicts, and of producing a corrupt file after an automatic merge.
There has been some research in this area, and there are a few semantic diffing tools[1,2,3], but I'm not aware of this being widely used in any VCS.
Nowadays, with all the machine learning advances, the ideal VCS should also use ML to understand the change at a deeper level, and maybe even suggest improvements. If AI can write code for me, it could surely understand what I'm trying to do, and help me so that version control is entirely hands-free, instead of having to fight with it, and be constantly aware of it, as I have to do now.
I just finished watching the presentation, and Pijul seems like an iterative improvement over Git. Nothing jumped out at me like a killer feature that would make me want to give it a try. It might be because the author focuses too much on technical details, instead of taking a step back and rethinking what a modern VCS tool should look like today.
[1]: https://semanticdiff.com/
[2]: https://github.com/trailofbits/graphtage
[3]: https://github.com/GumTreeDiff/gumtree
-
I added Go support to my VS Code extension for programming language aware diffs
You mean copying chunks from one file/side to the other? If that is the case, you might want to subscribe to this issue that was opened a few days ago. Since the extension does not work on a line-by-line level, it is a bit more difficult than for normal diffs. For example, what should happen if the formatting differs between both files. Should SemanticDiff copy it over as well or try to merge the changes? I will try to post an update on/in this issue soon and maybe have a discussion about the expected behavior.
- SemanticDiff – Language Aware Diff for VS Code
-
My Visual Studio Code extension for programming language aware diffs is now in public beta!
Feel free to open an issue at https://github.com/Sysmagine/SemanticDiff/issues so that we can keep you updated on the progress.
-
Searching for beta testers for my VS Code extension that makes diffs more readable
Feel free to open feature requests for any languages you need: https://github.com/Sysmagine/SemanticDiff/issues
What are some alternatives?
jupyter-vim-binding - Jupyter meets Vim. Vimmer will fall in love.
mergify - Merge git changes on commit at a time.
vscode-jupyter - VS Code Jupyter extension
git-machete - Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen
livebook - Automate code & data workflows with interactive Elixir notebooks
vscode-settings - My VS Code settings and extensions
jupyterlab-git - A Git extension for JupyterLab
graphtage - A semantic diff utility and library for tree-like files such as JSON, JSON5, XML, HTML, YAML, and CSV.
pyro - Deep universal probabilistic programming with Python and PyTorch
difftastic - a structural diff that understands syntax 🟥🟩
notebooks - Examples and tutorials on using SOTA computer vision models and techniques. Learn everything from old-school ResNet, through YOLO and object-detection transformers like DETR, to the latest models like Grounding DINO and SAM.
git-stack - Stacked branch management for Git