Skip to main content
Ryan Orban

Ryan Orban

Subject
26 entries

Git

Bookmarks

  1. git_bayesect: Bayesian git bisect for flaky tests

    Bayesian git bisect for flaky tests. Finally a way to handle probabilistic failures that standard bisect can't.

  2. GitAgent: git-native open standard for AI agents

    GitAgent defines AI agents as version-controlled files in a git repo — SOUL.md, SKILL.md, agent.yaml — exportable to any framework. The bet is that agent definitions should live in your repo, not a vendor's cloud.

  3. Difftastic: structural diff that understands syntax

    Difftastic is a structural diff tool that parses code with tree-sitter and compares syntax trees rather than lines, filtering out reformatting noise. Essential for anyone who's debugged a reformatted file in a unified diff.

  4. code.storage: git-backed code storage

    code.storage is a git-backed code storage service designed for scale. Minimal public information available at the time of capture.

  5. Letta Context Repositories: git-versioned memory for coding agents

    Letta introduces Context Repositories — git-versioned memory for coding agents that treats context as source code with branches, commits, and diffs. A substantive rethink of how stateful coding agents should manage long-lived context.

  6. roborev: continuous code review for AI agent commits

    roborev automatically reviews every commit an AI coding agent makes via git hooks, accumulating findings in a persistent queue. The problem it solves: agents write fast but move on before reviewing their own mistakes.

  7. Par: Parallel Worktree and Session Manager

    Par is a CLI that combines git worktrees with tmux sessions to manage parallel development workstreams — each task gets an isolated directory and persistent terminal. Built for concurrent AI-assisted development where multiple agents run simultaneously.

  8. Jujutsu For Busy Devs: Practical Intro to jj

    A pragmatic intro to Jujutsu (jj), the new version control system that's git-compatible but fixes many of git's ergonomic frustrations — written for developers who don't have time for a deep-dive. jj's working-copy-as-a-commit model and first-class conflict handling make it worth adopting.

  9. mrnugget's Git Helpers Dotfile

    Specific lines from Matej Hustau's (mrnugget) githelpers dotfile — a shell script of git log formatting and productivity aliases. A reference for clean git log output and workflow helper patterns from a seasoned developer's dotfiles.

  10. Piku: The Tiniest PaaS You've Ever Seen

    Piku is a tiny self-hosted PaaS that lets you git-push to deploy to your own servers — a minimal Heroku-style experience with no containers required. Under 2000 lines of Python, runs on any Linux server.

  11. Signing Git Commits with Your SSH Key

    A walkthrough of using your existing SSH key to sign Git commits instead of a GPG key — a feature added in Git 2.34. Signing git commits is good practice for supply chain security, and SSH keys are already part of most developers' daily workflow, making this a low-friction upgrade over GPG.

  12. DAGsHub: GitHub for Data Science

    DAGsHub is a GitHub-like collaboration platform for data science — adding data versioning (DVC), experiment tracking, and model registry to the familiar git workflow. Addresses the pain point that standard git doesn't handle large data files or ML experiment metadata.

  13. Radicle: Peer-to-Peer Code Collaboration

    Radicle is a peer-to-peer code collaboration stack built on Git — no central server, no platform dependency, repositories hosted on a distributed network. The decentralized alternative to GitHub for sovereign code hosting.

  14. Git Organized: A Better Git Flow

    A simple git workflow improvement: make changes freely on a branch with WIP commits, then git reset to the branch point and recommit in logically grouped chunks before opening a PR. Separates the messy work of development from the clean artifact of a review-ready commit history.

  15. How to Back Up Your Git Repositories

    A Medium guide on backing up git repositories — covering bare clone strategy, rsync to external storage, and hosting your own Gitea/Gogs instance. Addresses the risk of losing code when hosting platforms go down or accounts get banned.

  16. Data Science Meets DevOps: MLOps with Jupyter, Git, and Kubernetes

    Kubeflow's blog post on MLOps practices combining Jupyter notebooks, Git, and Kubernetes — the infrastructure side of making ML reproducible, collaborative, and deployable. Establishes the canonical MLOps stack for Kubernetes-based ML teams.

  17. GOMP: Git Branch Comparison Tool

    GOMP (Git COMPare) is a CLI tool for visually comparing files that differ between two Git branches — a focused alternative to git diff for branch comparison workflows.

  18. Git Pretty — Recovery Flowchart

    Justin Hileman's flowchart for deciding which git command to run when you're in a mess — a decision tree that starts with 'did you push?' and branches into the right cleanup command. The most-shared git recovery reference of its era.

  19. git-flight-rules

    A comprehensive guide by k88hudson covering what to do when things go wrong in git — structured as flight rules (NASA-style: if X happens, do Y). One of the most-starred git reference repos on GitHub.

  20. Why is

    Stack Overflow thread on why git pull creates problems in divergent branches — advocates for git pull --rebase or a fast-forward-only alias instead. A workflow habit that eliminates unnecessary merge commits from shared history.

  21. Git Tips from the Trenches

    A practitioner's collection of git tips beyond the basics — covering aliases, bisect, stash, reflog, and workflow patterns learned from actual team use. The kind of git knowledge that only comes from running into the same problems repeatedly.

  22. On Undoing, Fixing, or Removing Commits in Git

    Seth Robertson's choose-your-own-adventure guide to undoing git mistakes — a decision tree covering uncommitted changes, unpublished commits, and pushed history. The go-to reference when something has gone wrong in git.

  23. Learn Git Branching

    Learn Git Branching is an interactive visual tutorial for Git concepts — especially branching, merging, rebasing, and remotes. The best resource for building a mental model of how Git's DAG actually works.

  24. Git Data Mining with Hadoop

    WANdisco's post on mining git repository data at scale using Hadoop — applying distributed batch processing to version control history to extract patterns across large codebases. An early example of treating code evolution as a data science problem.

  25. Git (and Github) for Data

    Open Knowledge Foundation's 2013 post on using Git and GitHub for data versioning — exploring whether the version control model that worked for code could work for datasets. An early articulation of what became the data-as-code movement.

  26. Legit: Git Workflow for Humans

    Legit is a Python-based git extension by Kenneth Reitz that wraps git branch management in more human-friendly commands. It fills a real gap: git's branch model is powerful but the command interface is notoriously user-hostile.

All bookmarks