GitHub · Contoso Delivery

GitHub Real delivery, end to end

One business problem.
One team on GitHub.
Shipped to Azure.

Follow a real project from a rainy afternoon that costs a retailer money, all the way to running code on Azure — breaking the idea into epics, tracking it on a Project board, branching with intent, and proving every change before it ships.

7 interactive explainers 65 animated steps Built on a real repository

server.js ci.yml cd.yml

const express = require('express');
const { getWeather } = require('./azureMaps');
// one call, every city Contoso sells in
router.get('/api/cities', async (req, res) => {
const cities = await getWeather(req.query.q);
res.json(cities);
});

⎇ feature/#2-health-cities-endpoints ✓ 4 checks passed

The journey

From a business problem to production

Six connected stops. Understand why the app exists, break it into work you can actually assign, track it, branch for it, prove every change, and ship it to Azure. Follow the whole path, or jump straight to any stop.

Start here Step 0 — do this first, or the rest will not work 5 min Three of the six stops ask you to run real commands against a real repository. Take five minutes now: create the repo, choose who owns it, install the GitHub CLI and sign in. Set it up →

Done? Paste your repository URL and the whole journey will use it

🌧 A business problem ☁ Running on Azure

01why-contoso.md8 steps

Why Contoso Is Building This

The business case

Weather signalPromotionsOne API

Start the journey → 02plan-the-work.md9 steps

Plan the Work

Idea → epics → sub-tasks

EpicsSub-tasksTask lists

Open explainer → 03track-the-board.md10 steps

Track It on a Board

GitHub Projects

Board viewWork TypeSprints

Open explainer →

Your toolkit · not a stop on the rail

Build It with Copilot

The board is full, so somebody has to write the code. Plans and pricing, Ask/Plan/Agent, and handing issue #2 to the cloud agent — then straight on to branching.

Free vs paidAI creditsAsk/Plan/AgentCloud agent

Open explainer → 04branch-strategy.md13 steps

Branch with Intent

main → epic → feature

Protected mainEpic branchesPR reviews

Open explainer → 05.github/workflows/ci.yml10 steps

Shift Left

Pipeline, tests & security

testsCodeQLsecrets→✅

RunnerCodeQLSecrets

Open explainer → 06.github/workflows/cd.yml7 steps

Ship It to Azure

CD, Service Principal & deploy

imageidentitydeploy→☁️

GHCRService PrincipalOIDC

Open explainer →

Start here

The spec this journey is built from

Every screen, endpoint and check in this journey comes from one short requirements document. Download it, then follow along — the official GitHub and Microsoft pages cover the mechanics.

Requirements (PDF) ↓ About Projects ↗ OIDC to Azure ↗

Where this can take you

GitHub certifications

Six GitHub credentials, all delivered through Microsoft Learn. This journey lines up most closely with GH-900 and GH-200 — the rest are where you go next.

GH-900 GitHub Foundations Git, repositories, collaboration and project management — written for developers and non-developers alike. View certification ↗

GH-200 GitHub Actions Author, troubleshoot and secure workflows — the CI/CD you meet in Shift Left and Ship It to Azure. View certification ↗

GH-300 GitHub Copilot Responsible AI use, Copilot plans and features, prompt engineering, privacy and content exclusions. View certification ↗

GH-500 GitHub Advanced Security Secret Protection, supply chain security and CodeQL code scanning — find, triage and remediate. View certification ↗

GH-100 GitHub Administration Running GitHub Enterprise: identities and access, SAML and SCIM, policies, runners and licensing. View certification ↗

GH-600 Agentic AI Developer Operate and supervise AI agents inside the software lifecycle, with GitHub as the control plane. View certification ↗

Exam codes and titles as published on Microsoft Learn. Each exam requires a score of 700 to pass.