github-multi-account

Setting up GitHub multi-account aliases involves detecting your authenticated accounts via gh auth status and confirming which are personal or work. The process generates PowerShell profile updates and wrapper scripts to enable seamless profile switching.

Yes, you can automatically switch between multiple GitHub accounts in PowerShell. The skill applies profile updates and PATH adjustments to create wrapper scripts, allowing you to switch between personal and work environments with simple commands.

Yes, you need gh auth status to configure multiple GitHub accounts. The skill requires detecting your authenticated accounts through the GitHub CLI before prompting you to assign personal or work labels and applying the alias configuration.

The best way to separate work and personal GitHub accounts on Windows is to use account-locked aliases. This skill automates the configuration by updating your PowerShell profile and generating wrapper scripts for clear environment separation.

The GitHub multi-account alias setup handles PowerShell profile updates by automatically generating and applying the necessary modifications. It adjusts your PATH and creates wrapper scripts to ensure account switching commands function correctly across environments.

If your GitHub aliases are not working after switching accounts, it may be due to incomplete PowerShell profile updates or PATH adjustments. The setup requires proper configuration of wrapper scripts to ensure account-locked environments function correctly.