AI-enabled developer productivity, build systems, and engineering leadership
Posted on in Programming
git show <revision> is handy because it combines commit metadata and a patch. Mercurial does not use the same command name, but its composable commands make the equivalent clear: use hg log for the changeset description, hg diff -c for the patch, and hg export when the result needs to …
Posted on in Programming
Remote-tracking branches are Git's cached view of branches on another server:
origin/feature/login, not your local feature/login. When a branch is deleted
on GitHub or GitLab, Git does not remove that cached name until a fetch with
pruning asks it to. The result is familiar: a branch appears …
Posted on in Programming
A repository move does not require throwing away a useful clone. If the project moves organizations, changes hosts, or is renamed, your local branches, stash, reflog, hooks, and unpushed work can stay right where they are. Update the remote deliberately, verify it, and then decide whether the branch topology also …
Posted on in Programming
Multiple GitHub accounts on one laptop are normal now: a managed work identity,
a personal account, perhaps an open-source organization account. The failure mode
is still surprising. git fetch says the repository does not exist even though
it absolutely does, because SSH offered a key that authenticated successfully
for the …
Posted on in Programming
The default history view in Git and Mercurial is optimized for completeness, not scanning. A compact one-line log is a better daily tool: short ID, subject, relative date, author, and branch or bookmark context. It does not replace a full graph; it makes the first pass fast enough that you …
