oxen-release
git-branchless
Our great sponsors
oxen-release | git-branchless | |
---|---|---|
22 | 55 | |
831 | 3,306 | |
9.9% | - | |
9.0 | 9.4 | |
29 days ago | 8 days ago | |
Python | Rust | |
Apache License 2.0 | Apache License 2.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.
oxen-release
-
Ask HN: Can we do better than Git for version control?
We've been working on a data version control system called "oxen" optimized for large unstructured datasets that we are seeing more and more with the advent of many of the generative AI techniques.
Many of these datasets have many many images, videos, audio files, text as well as structured tabular datasets that git or git-lfs just falls flat on.
Would love anyone to kick the tires on it and let us know what you think:
https://github.com/Oxen-AI/oxen-release
The commands are mirrored after git so it is easy to learn, but optimized under the hood for larger datasets.
-
Snakemake – A framework for reproducible data analysis
Super cool! Would love to see an integration with Oxen and their data version control https://github.com/Oxen-AI/oxen-release
-
Ask HN: Data Management for AI Training
We have been working on a data version control tool called Oxen that is tackling many of your needs. Feel free to check it out here:
https://github.com/Oxen-AI/oxen-release#-oxen
Going down your list of requirements, Oxen has:
* Data versioning, similar paradigm to git, but built from the ground up for large ML datasets
-
A tale of Phobos – how we almost cracked a ransomware using CUDA
We've been working on some open source tooling called "oxen" that was built for large datasets of images, video, audio, text etc. We wanted to solve the exact problem you're flagging here with git.
Feel free to check it out here https://github.com/Oxen-AI/oxen-release#-oxen would love any feedback!
- Oxen.ai: Fast Unstructured Data Version Control
- A versioning system for ML data sets
- Oxen - Version control for your machine learning datasets
git-branchless
-
Ask HN: Can we do better than Git for version control?
Yes, but due to its simplicity + extensibility + widespread adoption, I wouldn’t be surprised if we’re still using Git 100+ years from now.
The current trend (most popular and IMO likely to succeed) is to make tools (“layers”) which work on top of Git, like more intuitive UI/patterns (https://github.com/jesseduffield/lazygit, https://github.com/arxanas/git-branchless) and smart merge resolvers (https://github.com/Symbolk/IntelliMerge, https://docs.plasticscm.com/semanticmerge/how-to-configure/s...). Git it so flexible, even things that it handles terribly by default, it handles
- Meta developer tools: Working at scale
- Show HN: Gut – An easy-to-use CLI for Git
-
Branchless Workflow for Git
> Is this for a case where a bunch of people branch from master@HEAD (lets call this A), then you need to modify A, so you then need to rebase each branch that branched from A individually?
Mainly it's for when you branch from A multiple times, and then modify A. This can happen if you have some base work that you build multiple features on top of. I routinely do this as part of rapid prototyping, as described here: https://github.com/arxanas/git-branchless/wiki/Workflow:-div...
`git undo` shows a list of operations it'll execute, which you have to confirm before accepting. Of course, it's ultimately a matter of trust in the tools you use.
- Where are my Git UI features from the future?
- git-branchless: High-velocity, monorepo-scale workflow for Git
- git-branchless
-
Show HN: Maiao, Stacked Diffs for GitHub
What happens is you work somewhere that has stacked diffs and suddenly you learn how to shape your diffs to make them easy to review. Thinking of how folks will review your code in chunks while writing it makes it cleaner. Having small but easy to read diffs makes reviews faster and helps junior devs learn how to review.
Sometimes this doesn’t happen in which case you end up need to split your commit at the end. This is where git utterly fails. You end up needing git split and git absorb to make this productive.
Git split let’s you select which chunks in a commit should belong to it and then splits that into a commit and then you do it again and again until you have lots of commits. You’ll still need to probably test each one but the majority of the work is done
Git absorb takes changes on the top of your stack and magically finds which commit in your stack the each chunk should belong to and amends it to the right commit
You also need git branchless https://github.com/arxanas/git-branchless as it lets you move up and down the stack without needing to remember so much git arcana.
- High velocity, monorepo-scale workflow for Git
What are some alternatives?
VFSForGit - Virtual File System for Git: Enable Git at Enterprise Scale
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
gpt-2-output-dataset - Dataset of GPT-2 outputs for research in detection, biases, and more
jj - A Git-compatible VCS that is both simple and powerful
dvc - 🦉 ML Experiments and Data Management with Git
magit - It's Magit! A Git Porcelain inside Emacs.
dud - A lightweight CLI tool for versioning data alongside source code and building data pipelines.
vimagit - Ease your git workflow within Vim
mandala - A powerful and easy to use Python framework for experiment tracking and incremental computing
lazygit - simple terminal UI for git commands
dolt - Dolt – Git for Data
libgit2 - A cross-platform, linkable library implementation of Git that you can use in your application.