Detect and isolate active GitHub identities with gh auth status and GH_CONFIG_DIR.
npx skills add https://github.com/chdaly/eshop --skill gh-auth-isolation-chdaly
Please help me install this Agent Skill. Skill: gh-auth-isolation Source: https://github.com/chdaly/eshop/tree/main/.copilot/skills/gh-auth-isolation Command: npx skills add https://github.com/chdaly/eshop --skill gh-auth-isolation-chdaly
GitHub authentication in multi-account environments often mixes Enterprise Managed User (EMU) and personal identities, causing operations to run under the wrong account. This Skill teaches agents how to detect the active identity, switch contexts safely, and avoid credential leakage or unintended cross-account actions.
Ensure the active identity is correct, configure an isolated gh context, and perform the desired GitHub operation.
High-intent search queries and answers about installing and using this skill.
You can isolate GitHub identities by applying non-persistent context isolation via separate GH_CONFIG_DIR configurations. This approach detects the active identity using gh auth status and prevents credential leakage during multi-account operations.
The gh auth status command detects the active GitHub identity, enabling safe switching between EMU enterprise accounts and personal accounts. It ensures operations like pushes and PRs run under the correct account without mixing credentials.
The best way to switch accounts for a single operation is to extract a per-operation token using gh auth token within an isolated gh context. This allows you to perform pushes or PRs from the correct account without modifying the global environment.
Yes, you can safely manage multiple GitHub accounts in agent workflows by implementing identity detection and per-command resets. This isolates the active identity and prevents unintended cross-account actions during repository management.
Operations run under the wrong account when GitHub authentication mixes EMU and personal identities in the global environment. Isolating the active identity with separate GH_CONFIG_DIR configurations prevents this credential leakage.
dotnetIdentify active GitHub auth identity and isolate credentials per repository operation.
bdsqqqStage modified files, commit with conventional commits, and push to the remote repository.
jperezdelrealIsolate GitHub identities across automated workflows using gh auth status and GH_CONFIG_DIR.
QuintenpsConfigure GitHub CLI authentication switching with shell aliases and wrappers.
