One-to-one coaching · not a group course

Stop babysitting your pipeline.
Make GitHub run itself.

You've become the de facto GitHub admin with no formal training — permissions nobody remembers granting, a CI workflow one person is scared to touch. Over a four-week sprint, working directly with me one-to-one, you'll bring your org and your pipelines under real control.

Before
Manual deploys, tribal-knowledge permissions, one flaky workflow nobody dares touch.
After

Branch protection enforced, not hoped for
CI that fails loudly and gets fixed fast
Deploys anyone on the team can trust

Apply for a sprint

Some GitHub experience expected. No credit card. Just your email.

The reframe

You don't need a new job title. You need repeatable patterns.

Every excuse for leaving this until later has the same shape. Here's the honest version.

The myth
"I'd need to be a proper DevOps engineer to own this properly."
The reality
You need a handful of repeatable patterns — teams, permissions, branch protection, rulesets — not a new job title. We build them in week one.
The myth
"GitHub Actions is just YAML tinkering until something works."
The reality
Treated properly, a workflow is version-controlled infrastructure. Same discipline as the code it builds — not a chore bolted on afterward.
The myth
"If I lock things down, I'll slow the team down."
The reality
Good guardrails — clear ownership, enforced review, a pipeline people trust — make a team faster, not slower. Ambiguity is what actually costs time.
By the end

Three real things you'll have built

Not toy exercises — changes that go live in your actual GitHub org, on repos your team already uses.

Outcome 01

A hardened GitHub org

Teams that map to how work actually happens, permissions that make sense, and branch protection plus CODEOWNERS that actually get enforced — not just recommended.

Outcome 02

A real CI/CD pipeline

Build, test, and deploy running automatically on every push, using GitHub Actions — replacing whatever manual steps currently only you remember how to do.

Outcome 03

A reusable workflow your team can trust

A packaged, documented action or reusable workflow other repos can call — built and reviewed with me, one-to-one, in your final week.

Weeks 1–4 · Foundations

How the four-week sprint runs

One session with me each week, real changes to your real org in between, and a deliverable due by the end of every week.

WK 01

Org structure that makes sense

How organisations, teams, and repos relate to each other, and an honest audit of what's currently a mess — orphaned repos, forgotten collaborators, admin rights nobody remembers granting.

WK 02

Access control that actually holds

Branch protection, CODEOWNERS, and permissions that route review to the right person automatically — instead of relying on memory or urgency.

WK 03

Security and compliance basics

Secret scanning, Dependabot, and the audit log — catching leaked credentials and vulnerable dependencies before they become an incident.

WK 04

Governance that scales without you

Repo templates and rulesets that set the default, plus a short doc so this doesn't live only in your head — and can survive you being on holiday.

Weeks 5–8 · Optional next step

When you're ready, there's a Level 2

Foundations gets your org under control. Level 2 is a follow-on sprint for graduates who want to automate what they've just brought order to, with GitHub Actions — still just the two of us, one-to-one.

Week 5–6

Building real pipelines

Workflow fundamentals, multi-job pipelines, artifacts, and deployment gates — taking a commit from push to a live deployment, not just a passing test.

Week 7–8

Custom actions and org policy

Reusable workflows, self-hosted runners, OIDC instead of long-lived secrets, and a custom action published for your team, backed by an org-wide Actions policy.

Level 2 opens once you've finished Foundations. Apply below and mention you're interested in going further.

What we'll cover

Across administration and automation

Not a tour of every GitHub feature — the specific set that turns a chaotic org into one people trust.

Teams, permissions & repo visibility
Branch protection & CODEOWNERS
Secret scanning & Dependabot
Rulesets & repo templates
GitHub Actions workflows & pipelines
Reusable workflows & custom actions
Self-hosted runners & OIDC
Fit check

Who this is for

This is for you if

  • You're the de facto GitHub admin with no formal training in the role
  • Your CI is a pile of copy-pasted YAML nobody fully understands
  • You'd rather have direct, one-to-one attention than sit in a group
  • You can commit 3–4 hours a week for a month

This isn't for you if

  • You're already running a mature internal platform team — you'll want something more advanced
  • You're looking for a passive, watch-only video course
  • You want a group class or a community of peers as part of the format
  • You need Enterprise-specific features like SCIM or advanced auditing covered in depth
One-to-one, not a class

Book a sprint

This isn't a course you sit in with a group — it's four weeks of direct, one-to-one coaching on your actual GitHub org. I work with one person at a time, so I only take on a handful of sprints each month.

£999   £749 for a founding-client sprint · Foundations (Weeks 1–4)

Weekly 1:1 session plus async support for genuine blockers between sessions, wherever you are in the world.

Total: £749

No spam. Just a reply from me to see if it's a good fit.

Questions

Before you sign up

Do I need formal DevOps experience?

No, but you should already be comfortable using GitHub day-to-day — pushing code, opening PRs, reviewing changes. This isn't a "what is Git" course; it's for people ready to own the org and the pipeline, not just their own repos.

Does this cover GitHub Enterprise features?

The core sprint focuses on features available on GitHub Team, which covers most of what small-to-mid orgs need. Enterprise-only features like SCIM provisioning or advanced audit log streaming can be covered as a bonus session if you need them.

How much time do I need each week?

Plan for one 1:1 session plus 2–3 hours applying changes to your own org or repos. The work happens on your real GitHub setup, not a sandbox, so it's time you'd likely spend fixing this eventually anyway.

What if my org already has some of this in place?

Common, and fine — week one starts with an honest audit of what's already working, so we spend the sprint on the actual gaps rather than rebuilding what doesn't need it.

What if something breaks between sessions?

Standard support covers genuine blockers with a best-effort reply. If your pipeline or org can't wait — say a broken deploy blocking your team — Priority Support is an optional add-on with unlimited ad-hoc messages and a reply within 1 business day, for the full four weeks.