Git

Setting up a robust developer or systems administration workstation often requires working across both native Windows (PowerShell) and a Linux subsystem (WSL). Because version control coordinates configurations, automation scripts, and application source code, having Git installed and configured correctly in both environments is a fundamental prerequisite. Without deliberate setup, administrators frequently encounter annoying friction: entering GitHub or GitLab personal access tokens repeatedly inside WSL, running into permission errors on cross-mounted drives (/mnt/c/), or corrupting shell scripts because Windows inserted carriage return (CRLF) line endings into bash scripts. ...

For many system administrators, version control began as a folder full of scripts named backup-script-v1.ps1, backup-script-v2-final.ps1, and backup-script-v2-final-REALLYFINAL.ps1. Moving to Git solved local versioning, but modern IT operations require central collaboration, peer review, backup, and automated deployment. This is where GitHub becomes indispensable. GitHub transforms isolated scripts on administrator laptops into structured, collaborative infrastructure. Whether you manage PowerShell modules, Terraform definitions, Docker containers, or static documentation sites, understanding how GitHub works—and how to interact with it securely—is essential. ...