# test\(server\): pin git config for fixtures and compare native realpaths · pingdotgg/t3code

[View on GitCafe](https://git.cafe/pingdotgg/t3code/commit/11da79bf1749dd38c5d89072ca3db3b5a684400f)

Repository: [pingdotgg/t3code](https://git.cafe/pingdotgg/t3code)

Visibility: public

Requested revision: 11da79bf1749dd38c5d89072ca3db3b5a684400f

Requested commit: 11da79bf1749dd38c5d89072ca3db3b5a684400f

Commit: 11da79bf1749dd38c5d89072ca3db3b5a684400f

Tree: 942c5f28428ddf1fb448b0001d18a069efbb3a85

Author: Julius Marminge

Committer: Julius Marminge

## Message

```
test(server): pin git config for fixtures and compare native realpaths

Git for Windows installs with core.autocrlf=true, so every repository the
suite creates checked committed LF files out as CRLF and byte-exact content
assertions in GitManager, CheckpointReactor, and the orchestration engine
integration test compared 'v2\r\n' against 'v2\n'. A vitest setup file
now pins autocrlf, filemode, longpaths, gpgsign, and the default branch
through GIT_CONFIG_* so every git child the driver spawns sees them, ahead
of whatever the host's ~/.gitconfig says.

Two tests compared an Effect realPath of os.tmpdir() against git's own
report of the same directory; on GitHub's Windows runners the temp dir is
spelled with its 8.3 short name (RUNNER~1) and only realpathSync.native
expands it. The newline-in-worktree-path test is skipped on Windows, where
NTFS rejects the name outright.

Co-Authored-By: Claude Code <noreply@anthropic.com>

```

## Parents

- [4c642ebd4f8cd9ef61e2fc03210ea536506be7ac](https://git.cafe/pingdotgg/t3code/commit/4c642ebd4f8cd9ef61e2fc03210ea536506be7ac?format=markdown)

[Source at this commit](https://git.cafe/pingdotgg/t3code/tree/11da79bf1749dd38c5d89072ca3db3b5a684400f?format=markdown)