Skip to content

Keep Git initialization explicit in work folders - #748

Open
igorcosta wants to merge 1 commit into
mainfrom
optional-git-startup
Open

igorcosta wants to merge 1 commit into
mainfrom
optional-git-startup

Conversation

@igorcosta

@igorcosta igorcosta commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

Starting chat or file work in an empty folder used to run git init and, on macOS, create an ignore file before the composer appeared. Startup now only detects existing repositories; Git is optional until the person explicitly chooses a Git operation.

The legacy initialization result remains false, existing branch detection stays in place, and the normal startup path keeps its instructions and integrations. Squad's RPC startup already routes before this branch; this fixes normal terminal startup for the next CLI release.

Validation:

  • Updated startup regression failed in five cases before the fix; startup and branding suites now pass all 26 tests.
  • Built CLI Tuistory reaches the real composer in an empty folder and confirms no .git or .gitignore is created.
  • Full bun run proof: lint, type checking and 13,779 unit tests passed. Terminal stage: 531 passed, 3 failed, 2 skipped. Focused retry passed mouse/scroll and slash browsing (27 tests); Console connector synchronization still fails at toolsListed, also reproduced on the unmodified base 9d10d59. Aggregate proof is not green.
  • Build passes. ADR records the cause, RPC distinction and validation boundary.

GitHub CI on 3556fda completed successfully across the executed unit/terminal shards and macOS/Linux/Windows builds. The separate local aggregate-proof boundary above remains recorded; it was not relabeled as a passing local run.

Co-authored-by: Autohand Evolve <code-noreply@autohand.ai>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant