gh-auth-isolation

To switch GitHub identities, isolate credentials per account using token extraction methods and per-account config directories. This prevents cross-account contamination and ensures operations run under the correct identity without side effects.

Isolating gh config contexts involves setting up per-account config directories to separate credentials. This guarantees correct authentication and prevents cross-account actions when pushing to personal forks or creating PRs from personal branches.

Detecting the active GitHub identity works by verifying access and extracting per-account tokens before executing operations. This mechanism ensures that automated agent workflows perform actions under the correct account and avoid accidental cross-account operations.

You need to isolate GitHub authentication when performing operations that must run under a specific account within multi-account teams, such as pushing to personal forks, creating PRs from personal branches, or switching between EMU and personal accounts.

Yes, you can push to personal forks and create PRs without cross-account contamination by switching the authentication context to the desired GitHub identity before executing any gh command. This isolates credentials and prevents cross-account side effects.

Per-account gh config directories require proper token extraction and context switching before each operation. Without correctly isolating gh config contexts, automated workflows risk credential leakage and performing actions as the wrong account.