Add Windows troubleshooting for SSH agent conflicts.

[BlackDoubleB]

Add guidance for resolving passphrase prompts caused by Git for Windows using a different SSH client than the Windows ssh-agent.

Why

Users on Windows may configure ssh-agent in PowerShell but still be prompted for a passphrase when using Git operations. This can happen when Git for Windows uses its bundled SSH client, which cannot access the Windows ssh-agent service.

What's being changed

• Add a Windows TIP explaining the Git for Windows vs Windows OpenSSH mismatch.
• Include a command to configure Git to use the Windows system OpenSSH client:
  • git config --global core.sshCommand "C:/Windows/System32/OpenSSH/ssh.exe"

Check off the following

• I have reviewed the technical accuracy of the content in this PR.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md	fpt ghec ghes@ 3.19 3.18 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.19 3.18 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@BlackDoubleB Thanks for opening a PR! Let me check with the rest of the team about this and see what they think.