github-multi-account

You can manage multiple GitHub accounts by creating deterministic personal and work aliases for the gh CLI. This prevents friction and mistakes by replacing manual account switching with clear, account-specific shell wrappers.

Setting up PowerShell aliases involves auto-detecting logged-in accounts via gh auth status, confirming which username is personal or work, and generating shell profile functions to enable immediate use of ghp and ghw commands.

Yes, the configuration process runs gh auth status to identify multiple logged-in accounts, prompts you to map usernames as personal or work, and automatically generates the corresponding shell wrappers for safe repo operations.

The best way to prevent cross-account push errors is to enforce a rule to never use bare gh for repo operations, relying instead on generated account-specific aliases like ghp for personal repositories and ghw for work.

No, the automated shell environment setup creates PowerShell profile functions and cmd wrappers, automatically updates your PATH so the aliases are available immediately, and provides verification commands using gh api user.

You should avoid bare gh commands to prevent accidental pushes or API calls under the wrong identity. The setup specifies using account-specific aliases to ensure repo operations bind to the correct authenticated user.