Using Multiple GitHub Accounts: Automatically Select the Correct `gh` PAT Based on Repo Owner

Managing multiple GitHub accounts can be challenging, especially when it comes to selecting the correct Personal Access Token (PAT) for different repositories. When working with repositories from various owners, such as GitHub and another-user, Git Credential Manager or gh auth git-credential may default to the currently active account, resulting in errors like "Permission denied." To overcome this issue, GitHub CLI (gh) provides a solution that automatically selects the appropriate PAT based on the repository owner.

The core of this solution lies in modifying the .gitconfig file to include the `useHttpPath = true` setting. This allows the credential helper to receive the full repository URL, including the owner portion. Inside the helper, the first element of the path is extracted and used to retrieve the corresponding PAT with the command `gh auth token --user ACCOUNT`.

When accessing a repository like `https://github.com/aont/foo.git`, the command `gh auth token --user aont` is executed automatically, retrieving the correct PAT for that account. Similarly, for `https://github.com/another-user/bar.git`, the command `gh auth token --user another-user` is invoked. This process eliminates the need to manually switch accounts or use external scripts.

It's important to note that the `helper =` line should be added to the .gitconfig file, resetting any previously configured credential helpers. This ensures that only this specific helper is used when dealing with multiple GitHub accounts.

The same approach can be applied to Git repositories, allowing for seamless credential management across different repositories and services. By configuring the credential helper based on the remote URL, you can treat GitHub repositories and Gists with the same rules, making the process more efficient and streamlined.