🏛️GitHub Copilot Lab

Overview

This series trains IT administrators and DevOps practitioners to leverage GitHub Copilot across PowerShell, Python, YAML, Ansible, GitHub Actions, and language-to-language conversions. Each lab builds on prior work so participants finish with an end-to-end infrastructure automation pipeline while keeping roughly of hands-on time in PowerShell,n Python, and in YAML/Ansible. Participants will be guided to install the GitHub Copilot VS Code extension, follow the Setup.md for first-time setup, and then use GitHub Copilot to create and integrate PowerShell scripts, Python services, YAML configurations, Ansible playbooks, and GitHub Actions workflows.

Prerequisites

• Active GitHub Copilot subscription associated with your GitHub account.
• Latest Visual Studio Code release installed from code.visualstudio.com.
• Successful sign-in to GitHub within VS Code; review the authentication troubleshooting guide if needed.
• New to GitHub, VS Code, or Copilot? Follow the step-by-step Setup.md before Lab 1.

Installations required for local runtimes:

1. PowerShell 7+
2. Python 3.10+
3. Ansible Core via pip install ansible-core
4. Docker Desktop
5. YAML VSCode extension by Red Hat

Lab Roadmap

1. Lab 1 – PowerShell Automation with Copilot
2. Lab 2 – Python Automation with Copilot
3. Lab 3 – Ansible Playbooks with Copilot
4. Lab 4 – GitHub Actions CI/CD with Copilot
5. Lab 5 – Security Compliance as Code with Copilot

Environment Prerequisites

• GitHub Copilot enabled in Visual Studio Code.
• VS Code extensions: PowerShell, YAML, Ansible, GitHub Actions, GitHub Copilot Chat
• Local PowerShell 7+, Python 3.10+ with ansible-core, WSL(For Windows).
• Sample infrastructure target (Local, VM, container, or emulator) with SSH access.

Assessment & Deliverables

• PowerShell scripting showing Copilot-assisted iteration.
• YAML configuration pack (GitHub Actions, converted configs).
• Ansible collection with roles, handlers, and inventories.
• GitHub Actions workflow executing Ansible deployment.
• Security audit report and Best Practices documentation.

Copilot Engagement Playbook

1. Start with intent prompts (goal, constraints, environment).
2. Request code explanations before modifications.
3. Iterate via inline edits, then validate with lint/test tools.
4. Use Copilot Chat to translate between PowerShell ⇄ YAML ⇄ Ansible.

Repository Layout

├── docs
├── Lab1_PowerShell
├── Lab2_Python
├── Lab2_YAML
├── Lab3_Ansible
├── Lab4_GitHub_Actions
└── Lab5_Security
├── Readme.md
└── Setup.md