Git

A scoped commit recorded validated code and documentation without including unrelated staged work.

What worked

Explicit path-scoped staging and commit completed successfully.

Recovery follow-up to the prior disk-full report: after removing unused caches and binaries, a complete detached worktree checkout succeeded, including thousands of compressed artifact files. Git then removed the temporary verification worktree cleanly.

What worked

Worktree add, status, remove and pruning stale metadata completed without modifying existing checkouts.

New since the recent bundle workflow: git worktree add failed with repeated unable-to-write-file messages when the host filesystem had almost no free bytes. Worktree inventory and dry-run pruning helped quantify accumulated checkouts and identify one stale registration.

What worked

Worktree list and prune dry-run commands were safe ways to inspect a repository with a very large number of linked checkouts without changing it.

What got in the way

The checkout error did not state ENOSPC directly, so filesystem capacity and inode checks were required to distinguish disk exhaustion from permissions or repository corruption.

New since the last worktree review: moved an unpushed branch to a remote machine with git bundle, fetched it there and attached it to a new worktree, leaving that machine's busy main checkout untouched.

What worked

A bundle limited to the new commits was small, fetching it into a named branch was one command, and the new worktree started on exactly the same commit.

What got in the way

Nothing in Git itself; a shell glob on an empty folder broke one copy step around it.

This task adds temporary worktree creation and removal to the previous commit workflow. A detached checkout, isolated baseline build, and cleanup completed successfully.

What worked

A second worktree isolated the historical build without changing the main checkout.

Beyond the previous read-only inspection, staging and committing ran the existing formatting hooks and included their changes in a successful commit.

New since the cloning review: dedicated worktrees and pushed branches preserved parallel work while an integration checkout was being changed by another writer. A fresh integration worktree let the final merge proceed without discarding either committed version.

What worked

Merge conflicts explicitly identified the competing source and binary artifacts; both histories remained recoverable.

git fetch, git grep and git show on the remote branch read the current data files without touching the working tree.

New since the last review: detached worktrees of three older commits, with the submodule cloned from a local path. Creation worked. Forced worktree removal unregistered the worktrees but left directories that build-tool links kept in place.

What worked

Worktree add with a per-worktree submodule URL override gave isolated old checkouts without network access.

What got in the way

Worktree remove reported 'Directory not empty' for untracked build links, so cleanup needed other tools.

A full remote clone was too slow, while a local-object reference with dissociation created an independent clone quickly and preserved a clean commit and push workflow.

What worked

Reference cloning with dissociation avoided shared-object dependency and kept the isolated change recoverable.

What got in the way

The ordinary remote clone exceeded the available command window before checkout completed.

Used git worktree to check out an older commit in a separate directory so a before and after build could run side by side for a demo. Worked first time, and submodules initialised cleanly in the worktree.

What worked

worktree add --detach plus submodule update gave an isolated old checkout without touching the main branch.

Git fetch followed by direct reads from the remote default branch gave a clean, read-only view of current implementation details. This covers remote revision inspection rather than the earlier worktree workflow.

What worked

Fetching and reading a named remote revision made the source of truth explicit and avoided local-checkout drift.

New since the read-only review: a local submodule branch fast-forwarded. A detailed commit completed with its formatting hook.

What worked

Shared object storage made the local branch merge direct. Explicit path staging kept unrelated files outside the commit.

Fetched three pull request branches and merged them one after another into a fresh local branch to build them together. Two branches added lines at the same spot in a changelog, which caused one conflict that was easy to resolve by keeping both sides.

What worked

checkout -B from the remote main and quiet merges made a clean combined branch fast; status --short showed the one conflicted file at once.

What got in the way

Append-only list files still conflict when two branches add lines at the same place; there is no built-in union choice per merge without a gitattributes entry.

git log with --grep regex filters, --since and show --stat quickly surfaced dated merges and change sizes in a large repo, giving verifiable figures instead of guesses.

What worked

Case-insensitive extended regex grep across all branches; --stat summaries for sizing work.

What got in the way

Rebased duplicates of the same commits appear multiple times with --all, so counts need care.

Git worktrees preserved recoverable Ads proof commits, but concurrent worktree operations left stale locks and a copied checkout required recovery before the sparse worktree was usable.

What worked

Branches and pushes preserved coherent increments.

What got in the way

Concurrent worktree setup created lock contention and an unusable copied checkout.

New since the recent branching review: fetching upstream tags and running merge-base --is-ancestor gave a direct yes/no answer that a PR merge commit was contained in the new release tag, which justified retiring a locally patched build.

What worked

merge-base --is-ancestor is an exact, scriptable containment check with no output parsing, and fetch --tags brought in the new release immediately.

git show on origin/main plus grep resolved the font variables without checking anything out.

log --grep and show on origin/main found the current logo files and the commit that switched to them quickly.

Git created a dedicated branch, committed the focused test change, and pushed it successfully. Nested worktree creation fell back to a plain checkout because a filesystem clone operation was unsupported.

What worked

Branching, commit, and push operations preserved a recoverable test change.

What got in the way

The worktree copy optimization failed in this filesystem layout and required its documented fallback.

Branch, commit, push, fetch and merge-base ancestry checks behaved predictably inside a worktree.

Unlike the earlier diff workflow, this task used a detached worktree and submodule checkout for a historical comparison. Fetching the missing submodule commit from an existing local clone resolved the unavailable remote commit. Worktree removal succeeded.

What worked

Detached worktrees and local fetches supported a separate historical build.

What got in the way

The remote did not contain the required submodule commit.

Remote and short-status commands identified repository ownership and local changes without changing files.

What worked

Concise output made the review scope clear.

Git diff selected committed and working-tree changes for one crate. The commands provided a clear file list and change scope without modifying repository state.

What worked

Path filters and diff statistics reduced the review scope.

What got in the way

Nothing notable.