Best of Git — February 2026

1. 1
   Video

   ThePrimeTime·13w

   Why Epstein emails have so many ='s

   Equal signs appearing in the Epstein files are artifacts from MIME quoted-printable encoding combined with Windows text processing. RFC 2045 requires email lines to break every 76 characters using '=\r\n' soft breaks. When Windows processes these files in text mode, it converts CRLF to LF, leaving '=\n'. Two-pass email decoders then fail to properly decode the malformed sequence, leaving orphaned equal signs in the text where line breaks occurred.

   153

   14
2. 2
   Article

   Einenlum - Coding amongst alpacas and pinball machines·14w

   Git Shitstorm: How to Make Any Developer Lose Their Mind

   A developer created a prank tool called Git Shitstorm that silently corrupts Git history by randomly inserting code changes from the repository. The tool works by aliasing the git command and acting like Russian roulette—90% of the time it does nothing, but 10% of the time it selects random files, authors, and code snippets to inject into commits. Implemented in Go for speed, it adds minimal latency (under 100ms) making it nearly undetectable. The author emphasizes this is for educational and entertainment purposes only, warning against using it maliciously on coworkers' repositories.

   108

   11
3. 3
   Article

   Lobsters·10w

   Git in Postgres

   An exploration of storing git repositories inside PostgreSQL instead of the filesystem. The author built gitgres, a ~2,000-line C library implementing libgit2's object and ref database backends against Postgres via libpq. The git data model maps to just two tables (objects and refs), enabling SQL queries that join commit history with application data like issue trackers. The post argues this approach could simplify self-hosted forge deployments (targeting Forgejo/Gitea) by eliminating the split between a Postgres-backed web app and filesystem-based bare repos, enabling unified backups with pg_dump, row-level security for multi-tenancy, and NOTIFY-based push events. Storage overhead from lack of delta compression is acknowledged as a real trade-off, but the author argues operational simplicity outweighs it for small instances.

   81

   3
4. 4
   Article

   Zed·12w

   Split Diffs are Here — Zed's Blog

   Zed v0.224 ships split diff view as the new default, showing base code on the left and working copy on the right in synchronized scroll. Built on Zed's multibuffer architecture, the feature required solving two core challenges: keeping both sides vertically aligned across all changed files simultaneously, and maintaining performance at scale. Alignment is handled via a block map that inserts visual spacers between lines. Performance profiling uncovered broader wins including block map inefficiencies that sped up project search, and a macOS process spawning fix (switching from fork/exec to posix_spawn) that reduced main thread hangs from git blame and other external processes. Users can revert to unified diffs via the Diff View Style setting.

   75

   7
5. 5
   Video

   Theo - t3․gg·14w

   OpenAI just dropped their Cursor killer

   OpenAI released Codeex, a new AI coding tool combining CLI, web app, and desktop application for managing AI agents across projects. Unlike traditional code editors, it provides a GUI for orchestrating multiple parallel coding tasks, with features like work trees, cloud environments, automations, and cross-project thread management. The tool shares history between CLI and app, supports multiple editors, and enables developers to manage several concurrent development tasks simultaneously. While work tree implementation has limitations and environment variable management needs improvement, the orchestration layer represents a shift from direct code editing to agent management workflows.

   70

   8
6. 6
   Article

   Lonely Programmer·14w

   Git vs GitHub

   43

   13
7. 7
   Article

   Zed·13w

   How Our Community Shipped 66 Git Improvements In Under 2 Months — Zed's Blog

   Zed's eight-week community sprint "Let's Git Together" resulted in 66 shipped improvements to Git functionality, including 5 major features like file history view and tree view for the Git panel. The program paired Zed team members with community contributors through weekly pairing sessions and biweekly demo days, successfully addressing 28 bugs and 33 additional improvements. Key features included file history viewing, Git blame avatars for multiple platforms, remote management UI, and branch deletion capabilities, with contributors like @errmayank (10 contributions) and @Anthony-Eid (6 contributions) leading the effort.

   35

   2
8. 8
   Article

   Planet Python·11w

   How Even Senior Developers Mess Up Their Git Workflow

   Git merge conflicts aren't just a junior developer problem — even experienced developers fall into bad habits. Three non-negotiable Git practices can prevent most conflicts: using issue trackers with granular tickets to avoid coding in isolation, checking for open pull requests before branching (not just pulling from main), and mastering recovery commands like `git stash` and `git cherry-pick` for when things go wrong. The authors share a real-world example where they broke all three rules simultaneously while working on their book-tracking app, resulting in a painful weekend of manual conflict resolution.

   31

   1
9. 9
   Article

   Reinier·12w

   Claude Code Full Beginner Course: Learn Agents In 2026

   A comprehensive four-hour video course covering Claude Code from installation and IDE setup through advanced features like hooks, slash commands, and multi-agent workflows. Topics include project configuration with CLAUDE.md files, parallelizing work with sub-agents, Git worktrees for efficiency, token conservation through context management, and cloud deployment using Modal.

   19

   1
10. 10
    Article

    Markus Staab·13w

    Automate the process to find a regression commit

    Git bisect can be automated using the `git bisect run` command to find regression commits without manual intervention. The process involves creating a test script that returns exit code 0 for expected behavior and non-0 for failures, then running `git bisect run ./test.sh` to automatically identify the first bad commit. This eliminates human error and saves time compared to manually testing each commit during bisection.

    13

    1