--git

Grit: Rewriting Git in Rust with Agents

A few months ago I read about Anthropic's experiment of releasing a swarm of agents to write a functioning C compiler and it made me wonder about the feasibility of using that same approach to accomplish something I've been dreaming about for 15 years now, not long after we started GitHub - rewrite Git from scratch to be library based. Git is of course a very complex piece of software. There are lots of "plumbing" commands, lots of higher level commands - it was put together incrementally by...

No fix yet for critical RCE bug in open-source Git service Gogs - exploit module is out

Title: No fix yet for critical RCE bug in open-source Git service Gogs - exploit module is out There's a huge hole and no one is patching it thus far. A critical, remote code execution (RCE) bug in Gogs, a popular open-source self-hosted Git service, can be exploited by any authenticated user - no special privileges required - on a default installation to fully compromise vulnerable servers, steal credentials and multi-factor authentication secrets, or even modify code in hosted repositories in a wide-reaching supply-chain attack. A security researcher reported the 9.4-rated flaw to project maintainers in mid-March. It still doesn’t have a patch. It does, however, have a public Metasploit module - so we’d expect reports of in-the-wild exploitation to start very soon. The vulnerability affects all supported platforms, including Windows, Linux, and macOS, and installation methods, according to Rapid7 researcher Jonah Burgess, who found and reported the bug to Gogs maintainers via GitHub (GHSA-qf6p-p7ww-cwr9) on March 17. After they initially acknowledged that they received the report on March 28, Burgess says he never heard back from the Gogs team - not when he asked

Using Git's rerere feature to escape recurring conflict hell

Have you ever tried to merge two branches only to end up in conflict hell? You fix a bunch of conflicts only to run git merge --continue and be presented with the same conflicts. Repeat this process and after a few iterations you give up because it just isn't worth the pain and effort.

Sem: New primitive for code understanding – not LSPs, but entities on top of Git

Semantic understanding on top of Git. Diff, blame, impact, log. Functions, not lines.

Rift: Better Alternative to Git Worktrees

rift: better alternative to git worktrees - copy on write (saves space) - instant (< 0.1s on 10gb folder) - fast cli - use as FFI lib with bun or node mac and linux+btrfs for now more support soon npm install -g rift-snapshot # or bun add -g rift-snapshot Release archives are available from GitHub Releases. | Platform | Backend | Behavior | |---|---|---| | Linux x64 | Writable btrfs snapshots | rift init converts an ordinary directory into a btrfs subvolume.

Defeating Git Rigour Fatigue with Jujutsu

Local Git Remotes

Incident with Pull Requests, Issues, Git Operations and API Requests

Let's talk about EU Sovereignty (2025)

Let’s talk about EU Sovereignty First and foremost, I really dislike the term because it’s laden with all sorts of militaristic and anti-free movement and all sorts of other problematic baggage, but it’s the term the industry is using, so we go with it I guess until the current push is over and we can quietly suggest a different term like happened with git branch names and replication terms. It's also annoying to spell correctly.

Stop Using Conventional Commits

Posted on in Software Engineering • 1873 words • 9 minute read Tags: Git, Commits, Scoped Commits, Conventional Commits You’ve almost certainly encountered Conventional Commits before. It may have reared its ugly head in the changelog of an open source project you’ve used. It may have been the enforced commit format for an open source project you contributed to.