Test commits fail when GPG signing is enabled

[altendky]

Description

The test fixtures (tmpdir in unit tests and createTestProject in e2e tests) set up temporary git repositories but do not disable commit signing via git config. This causes test failures on developer machines configured with GPG/SSH signing agents (e.g., 1Password, pinentry-touchid).

The current state is inconsistent - some test files already use --no-gpg-sign while others do not. This makes it easy to introduce new failures when adding commits to tests.

Related:

• QOL - running e2e tests locally spams me with pinentry-touchid signing requests #18295 - same issue for e2e tests
• PR fix: don't sign snapshot commits #1046, PR fix: disable GPG signing in snapshot tests #3102 - prior partial fixes for snapshot tests

Plugins

N/A

OpenCode version

dev branch

Steps to reproduce

1. Configure git to use a signing agent (e.g., 1Password SSH agent, GPG with pinentry)
2. Run tests from packages/opencode: bun test test/project/project.test.ts
3. Tests fail with signing agent errors or spam pinentry prompts

Screenshot and/or share link

error: 1Password: agent returned an error
fatal: failed to write commit object

Operating System

Any (macOS, Linux, Windows)

Terminal

Any

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• QOL - running e2e tests locally spams me with pinentry-touchid signing requests #18295: Same root cause — e2e tests trigger GPG/pinentry signing requests on developer machines with commit signing configured. That issue also covers the pinentry spam problem from the same missing --no-gpg-sign configuration in test fixtures.

If this is intentionally a broader/different scope (e.g., unit tests in addition to e2e, or a more comprehensive fix), please clarify how it differs from #18295 so maintainers can decide whether to track them separately.