Git

This page is the front door to my dotfiles. It is written for one reader first: me, the next time I am sitting in front of a machine that does not know me yet. If you are someone else, welcome — take whatever is useful. Everything I care about in a terminal is in that repo: zsh with Powerlevel10k, tmux on a Ctrl+a prefix, Neovim through LazyVim, Ghostty in Catppuccin Mocha, lazygit, a git config that signs every commit, and the settings for the AI agents I work with every day, including a Claude Code status line that gets the bill right. None of it is copied into place. It is linked, so the repo stays the only copy, and a change on one machine is a git pull away from every other. ...

Syncing Obsidian vaults with Git works great until machine-specific files create conflicts or you accidentally commit sensitive notes. This guide gives you two battle-tested .gitignore configurations and a safety checklist to avoid common pitfalls. Quick take: Use the Strict setup to eliminate config conflicts entirely. Add .gitattributes for cleaner diffs. Keep your repo private unless you’re building a public knowledge base. Recommended .gitignore A) Minimal (Keep plugin settings, drop noise) Keeps plugin settings and config across devices. Excludes cache and workspace files. ...

Git submodules are a powerful feature that allows you to include and manage other repositories as part of your main repository. This is especially useful for projects where you want to use external repositories (e.g., a custom Neovim configuration) while keeping them independent. In this post, we’ll cover how to set up, update, and manage Git submodules with a practical example. What Are Git Submodules? A submodule in Git is a pointer to a specific commit of another repository. It allows you to include that repository as a part of your main project without merging its content directly into your repository. ...