libgit2
git-branchless
Our great sponsors
libgit2 | git-branchless | |
---|---|---|
30 | 55 | |
9,387 | 3,266 | |
1.0% | - | |
9.6 | 9.4 | |
6 days ago | 3 days ago | |
C | Rust | |
GNU General Public License v3.0 or later | 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.
libgit2
-
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative
Everything that is replicated on the network is stored as a Git object, using the libgit2[0] library. This library uses hardened SHA-1 internally, which is called sha1dc (for "detect collision").
[0]: https://github.com/libgit2/libgit2/blob/ac0f2245510f6c75db1b...
-
Speedbump – a TCP proxy to simulate variable network latency
This is delightful and I can't wait to try it out. Right now, the libgit2 project (https://github.com/libgit2/libgit2) has a custom HTTP git server wrapper that will throttle the responses down to a very slow rate. It's fun watching a `git clone` running over 2400 baud modem speeds, but it's actually been incredibly helpful for testing timeouts, odd buffering problems, and other things that crop up in weird network environments.
I'd love to jettison our hacky custom code and use something off-the-shelf instead.
- Things I just don't like about Git
-
Mold 2.0.0
I'm curious about the license change? This is an executable is it not? Invoking it as a separate process does not require you make the software calling it GPL so switching to MIT should have no affect in the common case.
If the authors really wanted a more permissive license, then instead of relicensing from AGPL to MIT they should have gone AGPL with linking exception. An example of a project that does this is libgit2 [1]. This licensing is more permissive but still permits the author to sell commercial licenses to those making closed-source code changes.
-
I'm feeling lazy today but want a better excuse than "working on documention" for the morning standup.
Using libxlsxwriter and libgit, it's straightforward -- just putting the equivalent of git shortlog and lines added and removed into a line of cells.
-
In-depth look: the Java try-with-resources statement
Sometime ago I started writing a JNI wrapper around libgit2.
-
Ask HN: Would more apps build with Git back-end if there’d be a solid SDK?
Have you seen [libgit2](https://libgit2.org/) and the csharp libgit2sharp? Both seem to be reasonable albeit low level interfaces to a repo.
My opinion is that you’ll still desire some other data store for indexing and searching as your application grows.
-
[Media] gitnu: git status enumerated
Though, as I was looking for possible improvements I stumbled upon https://libgit2.org and its rust bindings. That looks really exciting but it’s probably going to take too much time out of work.
- Ask HN: Is there a good tutorial on how to create a GitHub clone?
-
cl-git: a Common Lisp CFFI interface to the libgit2 library
Might be a cool project to update the bindings and get Common Lisp on the language bindings page https://github.com/libgit2/libgit2/issues/4907
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?
Rebasing is a fundamental primitive, but not Git's implementation of interactive rebasing.
I very much subscribe to a patch stack workflow, but have a great deal of difficulty doing advanced things in Git, because `git rebase -i` does not support enough workflows.
Here's some features which I've implemented which improved on `git rebase`.in general: https://github.com/arxanas/git-branchless/wiki/Command:-git-...
On the contrary: I myself have implemented these better operations, and they work great. They also exist in some other VCSes. You can see the `git-branchless` column in the table for comparison with the other clients.
- git reword: https://github.com/arxanas/git-branchless/wiki/Command:-git-...
- git move will perform the magic "see all downstream conflicts", but unfortunately will only show you the number of conflicting files, at present: https://github.com/arxanas/git-branchless/wiki/Command:-git-...
- You cannot undo arbitrary operations with the reflog (nor with `git reset`). See https://github.com/arxanas/git-branchless/wiki/Architecture#.... Besides those points, my `git undo` can even undo some working copy changes: https://github.com/arxanas/git-branchless/wiki/Command:-git-...
> The author's "features from the future" feel to me like they just haven't gotten a good feel for the model.
The author is apparently behind[1] a sucessful alternative UI to Git. It seems safe to assume that they are way beyond merely getting a feel for the Git model.
The Bad-UX denialism has really gone too far when authors like that are dismissed over the old You Just Have To Understand The Model talking point.
-
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.
What are some alternatives?
pygit2 - Python bindings for libgit2
graphite-cli - Graphite's CLI makes creating and submitting stacked changes easy.
jj - A Git-compatible VCS that is both simple and powerful
magit - It's Magit! A Git Porcelain inside Emacs.
lazygit - simple terminal UI for git commands
vimagit - Ease your git workflow within Vim
elfshaker - elfshaker stores binary objects efficiently
horde - Horde is a distributed Supervisor and Registry backed by DeltaCrdt
git-date - Bindings onto the date parsing code from Git
legit - Git for Humans, Inspired by GitHub for Mac™.
forgit - :zzz: A utility tool powered by fzf for using git interactively.
git-stack - Stacked branch management for Git