Is this instructor-led training?

No. Everything here is self-serve: the lessons and labs are free and complete, and the paid programme is a run-book a manager follows with their own team. There are no live sessions, and nothing requires a booking.

Do engineers need accounts?

No. There is no login. Progress is kept in each engineer's own browser under My Academy, and the team programme's assessment and checklists are files you run in your own tools.

What does GitHub Actions training look like here?

The GitHub Actions pillar covers fundamentals, CI for Python, Node, Go, Java, .NET and Docker, deployment, and a security cluster on permissions, injection, OIDC and supply chain. Four labs put it into practice: building Python, Node and Docker pipelines, and debugging one that has gone wrong.

What about GitHub security training?

Two pillars: Git Security & DevSecOps (repository security, secrets, signed commits, supply chain) and the Actions security cluster. The labs include auditing an unsafe workflow and migrating a stored cloud key to OIDC — the two changes with the largest effect on most teams.

How does developer onboarding work with the free material alone?

Pick a learning path — there are seven, from new-to-Git to enterprise scale — and have new engineers work through it with the labs. That is exactly what the paid programme sequences; the programme adds the assessment, checkpoints, standards template and manager checklists.

What does the programme cost?

Small Team (up to 10 engineers) and Engineering Team (up to 50) are one-time purchases listed on the product page. Larger organisations are handled on enquiry. Every tier includes the Professional Toolkit for each engineer.

Git & GitHub Training for Engineering Teams

Engineering teams do not have a Git knowledge problem. Every engineer has used Git for years. They have a Git consistency problem: eight people, eight mental models, and the differences only show up as an incident — a force push to main, a secret in history, a workflow that hands a fork write access.

This page is how teams use the Academy to fix that, from what is free to what is not.

Who this is for

Engineering managers, tech leads and platform teams responsible for how a group of developers works with Git and GitHub — typically 5 to 50 engineers, one or more repositories that matter, and at least one incident that should not have happened.

Start free: learning paths and labs

Everything a team needs to learn is published and free. Two things make it usable as team training rather than reading material:

Learning paths sequence it. Seven routes through the 300 lessons, chosen by where someone is now — new to Git, merging and rebasing, managing repositories, CI/CD, DevOps, AI-assisted engineering, enterprise scale. A team can agree a path and work through it together.

Labs make it practical. Twenty hands-on scenarios in a disposable repository: recover a deleted branch, undo a bad merge, configure CODEOWNERS and predict the routing, design a pull request workflow and test it, build Python, Node and Docker CI, migrate a workflow to OIDC, plan a Terraform change on a pull request. Each has real commands and real output.

Learning pathsSeven sequenced routes. Pick one for the team.

Hands-on labsTwenty scenarios, three tracks: Git repair, GitHub and CI, security and infrastructure.

GitHub Actions & CI/CDFundamentals through security, with a pipeline for every major language.

Git Security & DevSecOpsRepository security, secrets, signed commits, supply chain.

Find out where the team stands

Before choosing what to standardise, measure. The readiness assessment is twelve questions on workflow consistency, branching, pull requests, CODEOWNERS, rulesets, CI, secrets, OIDC, dependency security, onboarding, AI governance and GitOps. It scores in the browser and links the lesson for every gap.

Git & GitHub Team Readiness AssessmentFive minutes. Scored locally, nothing sent. Every gap becomes a link.

What a team gets from standardising

One workflow, written down — branching, merge method, commit and review conventions the team has agreed, instead of eight private habits.
Faster developer onboarding — a new engineer follows a sequence with checkpoints rather than absorbing habits by watching.
Fewer Git incidents — recovery, branching and history rules that prevent the force-push-and-scramble class of problem.
Better pull requests — templates, CODEOWNERS routing that works, and rules that make review non-optional.
GitHub governance you can audit — rulesets, required checks and a break-glass procedure instead of standing admin exemptions.
GitHub Actions standards — least-privilege permissions, pinned actions, a CI shape every repository follows.
Security practice as a default — secrets scoped to environments, OIDC instead of stored keys, push protection on.
AI-assisted engineering with review discipline — repository instructions, and agent pull requests reviewed with a checklist rather than a glance.

Every one of those is taught free. What a team usually lacks is the structure to make it stick.

When the free material is enough — and when it is not

Enough: a small team with a lead who will choose a path, run the labs together and write the team’s conventions down afterwards. Many teams need nothing more, and this page would be dishonest to suggest otherwise.

Not enough: when onboarding has to be repeatable across several hires and several managers; when you need to know per engineer where the gaps are; when the standards document needs to be agreed rather than improvised; when a manager needs a run-book rather than a reading list.

That is what the programme is.

The Engineering Team Onboarding System

A 30-day programme — four weeks with reading, a lab and a checkpoint each — plus a 19-skill assessment with a scoring guide, a Git standards template, governance and CI/CD checklists, and week-by-week manager and learner checklists. Every tier includes the Professional Toolkit for each engineer.

Engineering Team Onboarding SystemWhat it includes, pricing for 10 and 50 engineers, what it is not.

Professional ToolkitThe per-engineer templates every team tier includes.

Larger organisations

Organisation-wide licensing, internal distribution rights and adaptation of the standards material are agreed directly. The enterprise pillar — governance, identity, audit, fleet operations — is the free material those conversations usually start from.

ContactEnterprise terms, licensing questions, or anything this page did not answer.

Frequently asked questions

Is this instructor-led training?: No. Everything here is self-serve: the lessons and labs are free and complete, and the paid programme is a run-book a manager follows with their own team. There are no live sessions, and nothing requires a booking.
Do engineers need accounts?: No. There is no login. Progress is kept in each engineer's own browser under My Academy, and the team programme's assessment and checklists are files you run in your own tools.
What does GitHub Actions training look like here?: The GitHub Actions pillar covers fundamentals, CI for Python, Node, Go, Java, .NET and Docker, deployment, and a security cluster on permissions, injection, OIDC and supply chain. Four labs put it into practice: building Python, Node and Docker pipelines, and debugging one that has gone wrong.
What about GitHub security training?: Two pillars: Git Security & DevSecOps (repository security, secrets, signed commits, supply chain) and the Actions security cluster. The labs include auditing an unsafe workflow and migrating a stored cloud key to OIDC — the two changes with the largest effect on most teams.
How does developer onboarding work with the free material alone?: Pick a learning path — there are seven, from new-to-Git to enterprise scale — and have new engineers work through it with the labs. That is exactly what the paid programme sequences; the programme adds the assessment, checkpoints, standards template and manager checklists.
What does the programme cost?: Small Team (up to 10 engineers) and Engineering Team (up to 50) are one-time purchases listed on the product page. Larger organisations are handled on enquiry. Every tier includes the Professional Toolkit for each engineer.