FTP, a `my-plugin-final-v3-fixed` folder and the “last upload wins” rule. Sound familiar? It works until someone overwrites a teammate’s changes or breaks production on a Friday evening.
Git at the “add, commit, push” level ends at your first merge conflict. This course takes you further: from your first commit to team work through pull requests and automated deploys with GitHub Actions. No theory for theory’s sake: every command runs in a terminal right inside the lesson, and every topic comes with the questions interviewers actually ask.
Course path
What you’ll be able to do after each module
- Git basics: no change ever gets lost. You understand how Git stores changes and have a working repository.
- Daily workflow: a mistake costs a minute, not a panic. Meaningful commits, every change visible, anything can be undone.
- Branches: several tasks in parallel, conflicts become routine. You experiment in a branch without breaking working code.
- GitHub: sync without “last upload wins”. push, pull and fetch without losing anyone’s changes.
- Pull requests: code gets reviewed before it reaches main. You work in a team the way product studios do.
- Clean history: rebase and reflog without fear. You keep history readable and bring back “lost” commits.
- CI/CD: push → checks → deploy. No FTP and no manual uploads on a Friday evening.
How a lesson works
| Part | What you get |
|---|---|
| Short theory | only what you need for practice |
| Commands | ready-made examples from a real plugin project |
| Common mistakes | symptom → cause → fix |
| Terminal practice | commands run right in the browser, nothing to install |
| Interview questions | ready answers to the questions interviewers ask |
Who it’s for: WordPress developers who use Git “by feel” or still deploy over FTP.
Result: you work with Git in a team every day: branches, pull requests, code review, conflicts, clean history, automated checks and deploys with GitHub Actions.