// blog
Notes from building it.
Git internals, the pull-request loop across three forges, and what it takes to make AI optional in a tool people trust with their work.
- 2 min read
I use AI every day. My Git client still has an off switch.
GitDesktop is AI-native. One toggle hides all of it. On agency, trust, and the Git client that's left when the AI is gone.
- 10 min read
Will this merge conflict? Find out without merging
git merge-tree does the whole merge in memory and names every file that would conflict — without touching your working tree, your index, or your branch.
- 7 min read
The whole loop, one window: why I built this Git client
Pull requests that start before you push, branch updates without switching, and guardrails that aren't a pricing tier — the assumptions behind GitDesktop.
- 4 min read
Recovering a dropped stash: what git fsck can still find
A dropped or lost git stash is almost never gone. How to find it with git fsck, tell the real stash commit from its index twin, and get the work back.
Topics →
- git (13 posts) (13 posts)
- recovery (8 posts) (8 posts)
- workflow (5 posts) (5 posts)
- merge (3 posts) (3 posts)
- ai (1 posts) (1 posts)
- branches (1 posts) (1 posts)
- conflicts (1 posts) (1 posts)
- force-push (1 posts) (1 posts)
- pull-requests (1 posts) (1 posts)
- rebase (1 posts) (1 posts)
- reflog (1 posts) (1 posts)
- stash (1 posts) (1 posts)
- worktrees (1 posts) (1 posts)