Mac下借助gh CLI无缝使用多GitHub账户的配置问题

Your Current Config’s Limitations #

1. hasconfig:remote.*.url fails for clone: This rule only triggers after the repo’s remote is configured. When cloning a new repo, Git hasn’t set up the remote yet, so it defaults to your personal account—causing permission errors for work repos.
2. gh CLI credential helper depends on active account: The !gh auth git-credential helper uses whatever account is currently active in gh, forcing manual switches between accounts.

Yes, Your Desired Setup Is Possible #

We’ll fix this with directory-based configuration rules (so Git uses the right account from clone time) and gh CLI profiles to decouple credentials from the active account.

Step 1: Update Your Git Configs #

Main Config (~/.gitconfig)

Replace the remote-based includeIf with a directory-based rule, and specify your personal gh profile for credentials:

[user]
    name = My Name
    email = my-email@gmail.com
[credential "https://github.com"]
    username = my-personal-github-user
    helper = !gh auth git-credential --profile personal

[includeIf "gitdir:~/work/**"]
    path = ~/.git_config_work_org

• The --profile personal flag tells gh to use your personal account’s credentials for all repos outside ~/work/.

Work Config (~/.git_config_work_org)

Set work-specific user details and link to your work gh profile:

[user]
    name = My Name  # Keep consistent or adjust as needed
    email = my-email@work.com
[credential "https://github.com"]
    username = work-github-username
    helper = !gh auth git-credential --profile work

Step 2: Set Up Multiple gh CLI Profiles #

1. Authenticate your personal account with a dedicated profile:

   gh auth login --profile personal
   

   Follow the prompts to log in with your personal GitHub account.

2. Authenticate your work account with another profile:

   gh auth login --profile work
   

   Log in with your work GitHub account. Gh will store credentials for both profiles separately.

Step 3: Clone Repos to the Correct Directory #

• Clone personal repos anywhere outside ~/work/ (Git uses your personal config by default).
• Clone work repos directly into ~/work/—Git applies the work config immediately, even during clone:

  git clone https://github.com/WorkOrg/your-repo.git ~/work/your-repo
  

Why This Works #

• Directory-based includeIf: Git checks the target directory before setting up the remote, so clone operations use the correct account from the start.
• gh CLI profiles: Each profile has its own stored credentials, so you don’t need to switch active accounts—Git uses the specified profile via the credential helper.

Optional: SSH Alternative (More Secure) #

If you prefer SSH over HTTPS, set up ~/.ssh/config to map repo paths to specific keys:

# Personal GitHub
Host github.com-personal
    HostName github.com
    User git
    IdentityFile ~/.ssh/id_rsa_personal

# Work GitHub
Host github.com-work
    HostName github.com
    User git
    IdentityFile ~/.ssh/id_rsa_work

Clone repos using the host alias:

• Personal: git clone git@github.com-personal:MyUser/my-repo.git
• Work: git clone git@github.com-work:WorkOrg/your-repo.git
  This avoids credential helper issues entirely.

内容的提问来源于stack exchange，提问作者Randy Coburn