Git and GitHub in Practice: Version Control Teams Actually Use
Signature Course No. 455 — A Signature AI Socratic Coaching Course.
No experience needed — your coach starts where you are.
A New Kind of Learning
Socratic coaching, delivered by an agentic AI coach.
Not a course you watch. An AI coach you work with.
The Lighthouse Coach begins by discovering how you think about the subject, teaches what is missing, and gives you realistic practice before asking you to prove that you can use it. You may test out of concepts you already understand, while capstones turn the learning into a practical plan, decision, conversation, or other real-world result.
The curriculum is deliberately authored; the AI delivers it through coaching. It is not an AI randomly generating lessons.
A coach that teaches by asking — not by lecturing
The Lighthouse Coach is an AI Socratic coach built on Cognosco Learning's Git and GitHub in Practice: Version Control Teams Actually Use course, in the Personal Effectiveness & Well-Being category. It does not play videos at you. It holds a conversation: it asks you a question, listens to your answer, names the misconception it hears, affirms what you got right, and asks the next question — the way a great coach works in the room.
History is a shared account that other people will rely on. A repository is not your notebook. It is the team's memory of what changed, why it changed, who approved it, and how to get back to any earlier state on demand. This course teaches Git and GitHub as that team discipline: what a repository actually holds and how work moves through it, commits a colleague can trust, history read as evidence when something breaks, branches that isolate work without isolating people — and then the shared half of the craft, from honest synchronization to the written playbook a new hire can run on day one.
It starts with the repository itself. A repository is a recorded history — a chain of complete saved states, each carrying who made it, when, and why — and the files on your machine are one working copy of it. You will learn to name the state any change is in — edited, staged, committed, or pushed — and to ask the two questions the whole course runs on: which state is this in, and who else has it?
It works in two movements. First, Module 1 — The Record Itself — work through Concepts 1–9, finishing with The Repository Rescue Plan; then, Module 2 — Teams, Review, and Release — work through Concepts 10–18, finishing with The Team Version Control Playbook.
Both capstones produce real artifacts — a Repository Rescue Plan for an inherited repository whose record was treated as private scratch space: the audit of the record as found, the branch dispositions with their deciding reasons, the integration and synchronization settlement, the purge of what must never have entered, and undo at the right price; and a Team Version Control Playbook for a team of nine across two time zones: the branching model priced to the team's shape, the review and protection standard, reproducible releases, traceability from issue to tag, and recovery procedures written for a tired person at 2 a.m.
The honesty standard is part of the course. There is no programming instruction here and no command-reference manual: commands appear only as the vocabulary of the workflow — the commit, the branch, the merge, the push, the revert — taught at the level of the judgment each move carries. Where a platform setting is described, it is described as the decision it embodies, and the course tells you to verify the current setting in your own organization; what survives a product update is the judgment, and the judgment is what is taught.
The course is self-paced and always on — roughly 30 minutes per concept, about 9 hours in full, taken in as many sittings as you like. You can type your answers, or talk out loud: the Voice Coach speaks its questions and listens to your spoken replies. Learners who already know the material can test out concept by concept.
Git and GitHub in Practice: Version Control Teams Actually Use is part of The Lighthouse Signature Series — the online counterpart to the one-day, in-person learning Cognosco Learning delivers.
Course Facts
One full concept, coached end to end — free: verify your email and we’ll send you a link to start.
Already enrolled? Enter the course →
Diagnose → Learn & Practice → Prove → Capstone
Every learner moves through the same discipline a Cognosco instructor would insist on in the room.
Diagnose
The Coach starts where the course starts: with the repository itself. Say where the history in your current project actually lives — and if your machine and the shared drive both vanished tonight, what exactly the team could recover tomorrow; take the last change you made to shared work and name its state — edited, staged, committed, or pushed — and who besides you can see it; walk, honestly, the steps you actually take when the team needs to know what a file looked like two months ago. Every concept opens with three questions that locate where you actually stand, and your answers shape how deeply the Coach works the concept with you. Everyone begins with Module 1 — no skipping the foundations you only think you have.
Learn & Practice
Work each concept in conversation with the Coach — spoken or written — then practice it against realistic situations until it holds up.
Prove
Every concept ends in proof: answer the check cold and demonstrate the skill. Know it already? Test out and take credit immediately.
Capstone
Finish with two capstones — The Repository Rescue Plan for Module 1 and The Team Version Control Playbook for Module 2 — that pull the whole course together, and earn the certificate.
What You'll Learn
Which state is this in — and who else has it? Every skill in this course is those two questions asked at a different joint: the first disciplines everything you record, and the second prices everything you undo, rewrite, or force. A practitioner who asks both, every time, before acting will avoid most of the incidents this course describes — including several it describes happening to people who knew better.
Module 1 builds the record itself. The Repository and the Working Copy; The Commit as Communication; History as Evidence; Branching to Isolate Work; Merging and Integration; Conflicts and Their Judgment; Remotes and Synchronization; What Must Never Enter History; and Undo Without Damage — the moves one person makes, judged by the standard of the team that will read them later.
Module 2 governs the record in everyone's hands. Branching Models; The Pull Request; Reviewing Another Person's Work; Protecting the Shared Branch; Tags, Versions, and Releases; Issues and Traceability; Forks, Contributions, and Permissions; History Hygiene and Repair; and The Team Playbook — the agreements by which many people's records become one team's record.
And it holds its boundary throughout. How to write the material a repository holds — the programming, the platforms, the craft of building the thing itself — is taught in its own neighboring courses, which begin from the premise this course makes true: that your work already lives in a repository, your commits already explain themselves, and your team already knows how to recover when the shared record goes wrong. This course is the workflow underneath all of them.
What you will learn
- Explain what a repository holds and move work through its states deliberately
- Make commits that communicate — small, single-purpose, and explained
- Read history as evidence and find when, why, and by whom a change was made
- Isolate work on branches and integrate it without big-bang merges
- Resolve conflicts by intent, and synchronize with the remote honestly
- Keep secrets, bulk, and generated output out of history — permanently
- Undo mistakes at the right cost, for work that is private and work that is shared
- Choose and run a branching model, review flow, and protection standard a team can sustain
- Tag and release reproducibly, trace changes to their reasons, and set access at the level the work requires
- Repair history safely and hold the team's agreements in a written, tested playbook
Everything in the course
- All 18 concepts of Git and GitHub in Practice: Version Control Teams Actually Use, in 2 modules
- A starting-point check first — the Coach finds where you actually stand before teaching
- Learn, Practice, Prove for every concept — no passive video watching
- A test-out on every concept: prove you know it and move on
- The Voice Coach: talk with the Coach out loud — it speaks, listens, and replies
- A personal Learner Record of your work across the course
- Two capstone exercises: The Repository Rescue Plan and The Team Version Control Playbook
- A printable session summary whenever you pause
- The Lighthouse Coach completion certificate (Signature Series)
- Your progress is saved as you go — stop anytime, resume where you left off
Built for the people who keep the team's record
Developers and engineers — who use Git daily by imitation and feel the gaps exactly when an incident makes the gaps expensive; and team leads and engineering managers who own the branching model, the review standard, and the recovery when the shared branch breaks.
Technical writers, designers, data and operations staff — whose work lives in repositories too, and who are held to a workflow nobody ever taught them whole.
Students and new hires — who will be handed repository access in their first week and judged, silently, on how they treat the shared record. This course assumes you work, or are about to work, in a team repository on GitHub, and that you can perform the basic moves — clone, commit, push, open a pull request — at the level of following a reference; it assumes no particular programming language and teaches none.
Prefer to learn live and in person? The same material anchors Cognosco's one-day programs — browse the in-person catalog.
Start with The Repository and the Working Copy
$195 — introductory price. One payment. No subscription, no password to manage.
Here is exactly what happens when you enroll:
- Pay securely with Stripe — you are taken straight into the course
- Create your learner profile and begin the Module 1 starting-point check
- Save the access key you are given — it restores your enrollment on any device
- Learn at your pace; your progress is stored in your browser on your device
For the full voice experience, use Chrome and allow the microphone when asked. Typing your answers works everywhere, all the time. Questions before you enroll? Email hello@cognoscolearning.com.
Before you enroll
What is a Socratic coaching session?
A conversation, not a video. Your coach asks a question; you answer — out loud by voice, or by typing — and the coach responds to what you said: naming the misconception it hears, affirming what you got right, and asking the next question. You advance only when you have mastered each concept, so a finished course means the learning held.
How long does it take — and how long do I have?
About 30 minutes per concept. Learn in sittings of any length; your progress is saved as you go. You have a full year from purchase to finish, and you can revisit and retake within that year.
What does the certificate verify?
That you completed every concept and both capstones of this course. Anyone can confirm a Cognosco certificate online — enter its certificate ID on our verification page.
What if it isn't for me — what are the refunds?
If you have not started, cancel for a full refund within seven days of purchase. Once you have started, there is no cash refund — stop before finishing and we credit the full amount you paid toward any other course in the library (credit valid one year from your original purchase). Once you complete the course, no refund or credit applies.
More Signature Courses are coming
Git and GitHub in Practice: Version Control Teams Actually Use is Signature Course No. 455. Leave your email and we'll send you news of future Signature Courses and Lighthouse updates as they are announced — nothing else.