A DEVELOPER MADE A REAL COMMIT WITHOUT EVER TYPING GIT ADD OR GIT COMMIT -- JUST TO PROVE THE COMMANDS YOU LIVE BY ARE A THIN SHELL OVER A DATABASE YOU'VE NEVER ONCE OPENED55 minutes from Tim Berglund, a longtime Git teacher and GitHub evangelist, taking the tool apart down to… https://t.co/z8Tf4udInA pic.twitter.com/vJNRCmSBb9— slash1s (@slash1sol) June 4, 2026
isabel (@isabelroses.com)
alias fuggit="git add . && git commit --amend --no-edit && git push --force"
GitHub - unkeyed/unkey: The Developer Platform for Modern APIs
The Developer Platform for Modern APIs. Contribute to unkeyed/unkey development by creating an account on GitHub.
Ditching GitHub
This is going to be some sort of a public service announcement, withside notes. This has been brewing for a long, long time (years), it’sjust that I never se...
Introducing git-wt: Worktrees Simplified
In my previous post, I explained why the bare repo pattern makes git worktrees actually pleasant to use. But setting it up manually requires 10+ commands. And t...
Solving Git's Pain Points with Jujutsu (with Martin von Zweigbergk)
katelynsills/copyright-history
Every amendment to US copyright law (1790-present) as a git commit. Browse 236 years of legislation with git log, git diff, and git checkout.
crawshaw - 2026-05-07
The industry-established code review process, review-then-commit, was a straightforward mechanism that allowed a relatively low-trust group of engineers to collaborate. It appears to have been initially developed for the Apache server OSS project in the 90s, corporatized by Google in the early 2000s, and popularized throughout the industry by several means, most notable of which was the GitHub PR.
Commits · DataXResearch/rabbithole
Track your rabbitholes! Contribute to DataXResearch/rabbithole development by creating an account on GitHub.
A GitHub Issue Title Compromised 4,000 Developer Machines
A prompt injection in a GitHub issue triggered a chain reaction that ended with 4,000 developers getting OpenClaw installed without consent. The attack composes well-understood vulnerabilities into something new: one AI tool bootstrapping another.
A big part of Github's stickiness is the social proof + resume of your activity history. Is there an easy omni-identity that combines your GitHub, Gitlab, @tangled.org, and @radicle.dev activity into a single view? Might lower the risk of starting new repos on emerging platforms.
