Handle linked worktree git directories when GIT_DIR points to .git/worktrees/<name>.
Previously Repo() could fail with InvalidGitRepositoryError in this scenario,
while Repo(os.getcwd()) worked correctly.

Add regression test to cover autodiscovery in linked worktrees.

Bumps the pre-commit group with 1 update: [https://github.com/astral-sh/ruff-pre-commit](https://github.com/astral-sh/ruff-pre-commit).


Updates `https://github.com/astral-sh/ruff-pre-commit` from v0.15.8 to 0.15.12
- [Release notes](https://github.com/astral-sh/ruff-pre-commit/releases)
- [Commits](astral-sh/ruff-pre-commit@v0.15.8...v0.15.12)

---
updated-dependencies:
- dependency-name: https://github.com/astral-sh/ruff-pre-commit
  dependency-version: 0.15.12
  dependency-type: direct:production
  dependency-group: pre-commit
...

Signed-off-by: dependabot[bot] <support@github.com>

The Windows CI jobs for PR 2140 failed in
test/test_index.py::TestIndex::test_index_mutation. The failing checkout path
creates my_fake_symlink and Git for Windows 2.54 reports a symlink warning
before GitPython raises GitCommandError. This is the same unsupported Windows
symlink behavior that the test already marks as an expected failure when
core.symlinks is true.

Detect Windows hosts that can create symlinks directly and include
GitCommandError in the expected failure types, so symlink-capable Windows
runners do not fail this unrelated Dependabot PR.

Co-authored-by: Sebastian Thiel <sebastian.thiel@icloud.com>

…mit/pre-commit-c64bca4cd5

Bump https://github.com/astral-sh/ruff-pre-commit from v0.15.8 to 0.15.12 in the pre-commit group

Bumps [git/ext/gitdb](https://github.com/gitpython-developers/gitdb) from `335c0f6` to `53c94d6`.
- [Release notes](https://github.com/gitpython-developers/gitdb/releases)
- [Commits](gitpython-developers/gitdb@335c0f6...53c94d6)

---
updated-dependencies:
- dependency-name: git/ext/gitdb
  dependency-version: 53c94d682b541595918cea6fc2e96bb900eb0e8c
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

…les/git/ext/gitdb-53c94d6

Bump git/ext/gitdb from `335c0f6` to `53c94d6`

Fix Repo() autodiscovery in linked worktrees when GIT_DIR is set

GitConfigParser already rejected CR, LF, and NUL in config values before
writing, but section and option names could still reach configparser. Because
GitPython writes section headers itself, a newline-bearing section name could
split the output into additional headers.

Reject CR, LF, and NUL in section and option names on write paths that create
or set config keys: add_section(), set(), set_value(), add_value(), and
rename_section() destinations. This matches Git config key validation behavior;
Git source commit 94f057755b7941b321fd11fec1b2e3ca5313a4e0 reports invalid keys
containing newlines from config.c, and local git 2.50.1 rejects newline-bearing
config keys.

Add a regression test covering unsafe section and option names while preserving
safe writes.

Co-authored-by: Sebastian Thiel <sebastian.thiel@icloud.com>

…g-key-newlines

Validate config key names before writing

…ines.

Co-authored-by: GPT 5.5 <codex@openai.com>

Split the quality-expectations section into two paragraphs (the warning
about low-quality contributions being declined was visually merged with
the preceding paragraph). Replace "and the pull request closed without
warning" with a note that maintainers may not always be able to provide
detailed feedback, which conveys the same practical reality.

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

Add AI-disclosure and quality requirements to the contribution guidelines