gh-auth-isolation

To switch GitHub accounts safely, you isolate gh configurations and tokens per task, creating reversible context changes before performing any operations. This prevents cross-account contamination and accidental pushes to personal repos from agent workflows.

Identity detection determines which GitHub account is active and checks its specific scopes before performing actions. It identifies whether the active context is an EMU or personal account to ensure safe context switching.

The best way to manage multiple GitHub identities is isolating gh configurations and tokens for each task. This enforces best practices with explicit prompts and safe defaults for token handling and reversible context changes.

Yes, you can switch between EMU and personal GitHub accounts safely by isolating gh configurations per task. The process enforces reversible context changes and authentication status checks to preserve token handling integrity.

Accidental pushes to personal GitHub repositories occur due to cross-account contamination when contexts are not isolated. You need to isolate gh configurations and tokens per task and enforce safe defaults before operations.