Git/Version Control Basics for IT Workflow
Guide for IT Consultants
A practical introduction to Git and version control, explaining what it is, why it's useful, and how to implement it in your daily IT workflow.
What is Git?
Git tracks changes to files over time. Think of it like "Track Changes" in Word, but for any file type—especially code and scripts. Every change you make is saved as a snapshot you can go back to.
What is a Repository?
A repository (repo) is simply a folder that Git is watching. It contains your files plus a hidden .git folder that stores the entire history of changes.
What is GitHub?
GitHub is a website that hosts your repositories online. It gives you a backup in the cloud and lets you access your work from any machine.
Why would you use it?
As an IT consultant, you'd use Git for:
- PowerShell scripts - Track every change, revert if something breaks
- Documentation - Keep versions of policies, guides, procedures
- Configuration files - Store Intune policies, Power Automate JSON exports
- Client work separation - One repo per client keeps things organised
Real example: You write a script to disable user accounts. It works. Two weeks later you "improve" it and it breaks. With Git, you can see exactly what changed and roll back instantly.
Key terms (just 5 to start)
| Term | Meaning |
|---|---|
| Repository (repo) | A folder Git is tracking |
| Commit | A saved snapshot of your changes |
| Push | Upload your commits to GitHub |
| Pull | Download changes from GitHub |
| Clone | Copy a repo from GitHub to your computer |
Your basic daily workflow
- Make changes to your files
- Commit - Save a snapshot with a short description
- Push - Upload to GitHub for backup
That's it. Three steps.
Next steps
Once you're comfortable with this concept, we can set up a repository structure for your work (BCM scripts, guides, configs) and walk through the first commit in VS Code or terminal.