CI Needs a Return Address
I was copying review comments from GitLab into an agent chat. Being the mailman got old, so I built a watcher to deliver the feedback and remember what still needed attention.
Loading...
Git workflows, recipes, and the occasional sharp edge.
I was copying review comments from GitLab into an agent chat. Being the mailman got old, so I built a watcher to deliver the feedback and remember what still needed attention.
A practical post-checkout hook that keeps local Claude Code memory files available in every Git worktree without committing them to the repository.
Use Claude Code CLI to generate meaningful commit messages following conventional commits format.
Git uses the words ours and theirs from the point of view of the operation it is currently performing. That is why they mean one thing during merge and can feel reversed during rebase.
Any version control system exists to preserve every project change across its entire history, so a leaked password, token, or key will not disappear by itself. Here is the modern recipe: rotate first, then git filter-repo, then a coordinated cleanup of every copy.
Sometimes you need to keep working on old projects that may use outdated version control systems, such as Mercurial or, God forbid, SVN.
Put the branch name beside your working directory using Git’s own prompt helper. The missing step: load git-prompt.sh before calling __git_ps1.
Let Git remind you about migration files when you switch branches. This updated recipe compares the commits passed to post-checkout and leaves database migration tracking to your framework.
A small, current Git setup: identity, default branch name, editor, credential helper, and a few aliases that make day-to-day work less noisy.
It is always pleasant to start a project from scratch, create its repository yourself, define the coding style accepted in it, and much else. But sometimes we inherit difficult children with a heavy past: mixed tabs and spaces, different line endings, and encodings.