3 ms·
I admit the diagrams and struggles the author describes are far past my own usage of git. And like they identify at the end of the article, for truly complex gi
by vintagedave 5mo ago
I admit the diagrams and struggles the author describes are far past my own usage of git. And like they identify at the end of the article, for truly complex git operations today I use AI. I haven’t rebased manually for a while. Forget rewriting commit messages!
> Companies like Meta have enjoyed in-house systems that run circles around it for almost a decade.
Based on Mercurial… the VCS I enjoyed using.
- miguel_martin 5mo agoThere is an open source & git compatible version of Meta's VCS: https://sapling-scm.com/ https://sapling-scm.com/
- KingMob 5mo agoIIUC, jj was heavily inspired by hg. In particular, the revsets and the UI.
- surajrmal 5mo agoI use AI prolifically for coding, but I haven't crossed the chasm of letting it do mutable operations on my vcs. It tends to revert changes too eagerly. Commit messages written by it usually miss the point of the commit and end up too verbose and need to be modified or completely rewritten in many cases. I feel like prose needs to capture style which is unique per individual which makes it difficult to do well.
- cstrahan 5mo agoI agree on the commit messages not being ideal, though a bit of by-hand rewording goes a long way. Recently let Claude Code handle some commit history clean up: split a couple commits, reordered some, and identified some that could/should have been fixups, and reduced the number of commits from ~70 down to ~40. Very happy with the results and time savings. FWIW, here’s my interactive rebase skill: https://github.com/cstrahan/claude-plugins/blob/main/skills/git-rebase-interactive/SKILL.md https://github.com/cstrahan/claude-plugins/blob/main/skills/...