Repository navigation
Conversation
An untracked file under Assets/ compiles into every build made from the working copy and into none made from a fresh clone; #132 found such a build in the hands of testers. The first half (the stray diagnostic file) is already gone. The second half was only documentation: the scripts appended "-dirty" and carried on. build-mac.sh and build-linux.sh now stop before the Unity call when git status is not clean, with --allow-dirty as the explicit way out and --check-only for a dry run. --skip-build goes through the same check and compares against a sidecar Builds/<platform>/.build-commit written after a successful build, so a fresh commit label can no longer be stamped onto an old build. A HEAD that differs from origin/main is a warning only, and an offline fetch does not abort. The README documents the build location. Fixes #132. Decision D-124 (draft; binding with the merge). Shell counter-checks ran in a throwaway repo; no Unity build, signing or DMG step was exercised. Sim tests 778/778 (no C# change). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was:
build-mac.shundbuild-linux.shbrechen bei unsauberem Baum (git status --porcelain) vor dem Unity-Aufruf ab. Neu:--allow-dirty(Stempel behält-dirty),--check-only, SidecarBuilds/<Plattform>/.build-commitfür--skip-build. HEAD ≠ origin/main nur Warnung, offline robust. README 2.1.0 mit Bauort-Rezept.Warum: Teil 1 von #132 (untrackte
InputGateDiagnostic.cs) ist erledigt — die Datei existiert nirgends mehr. Teil 2 (Beta nur aus sauberem Baum) stand nur in der Doku. Fixes #132, Entscheidung D-124 (Entwurf).Bereiche:
tools/packaging/, DecisionLog, CHANGELOG. Kein Spielcode.Changelog:
[Unreleased]→ Geändert.Tests:
bash -n; Shell-Gegenprobe in einem Wegwerf-Repo (sauber/unsauber/--allow-dirty/--skip-buildmit und ohne Sidecar/offline);dotnet test778/778 (keine C#-Änderung);check_docs.pyOK.Unity-Spuren / echter Build: nicht gelaufen (kein Unity-Build, kein Signieren, kein DMG).
Spielabnahme: entfällt.
Review-Befunde (mittel, für den Inhaber): Baum wird nach dem Unity-Lauf nicht erneut geprüft; das Bauort-Rezept nennt nur skip-worktree auf
AssetMappingRegistry.asset, obwohl unterAssets/_Project/Art153 Dateien getrackt sind. Details:reports/v8.6.0/issue-lauf-2026-10-17/05b-review-1-issue-132.md.🤖 Generated with Claude Code