Delivery governance · GitHub-native · MIT
Ship with structure.
Stay on GitHub.
The GitHub Delivery Operating System (Delivery OS) is a framework for structured sprints, QA coordination, and collaborative production gates—embedded as workflows and templates inside your repository. No external orchestration SaaS required.
Why this exists
Teams often coordinate delivery informally in GitHub—manual approvals, uneven sprint tracking, and ad hoc production sign-off. As you scale, that creates ambiguity, QA bottlenecks, and release risk.
Delivery OS gives you repeatable intake, sprint orchestration, QA governance, and release gates—without replacing your CI/CD pipelines or how developers work day to day.
- Delivery ambiguity across teams
- QA bottlenecks and unclear ownership
- Informal production approvals
- Cross-repo inconsistency
Install in one command
From your repository root, install workflows and issue templates into the current repo:
npx github-delivery-os install --with-templates .
Add --with-labels to create labels with the gh CLI. Use --dry-run to preview. Existing files are skipped by default; use --overwrite when updating.
Also available: status, uninstall — see the repo README.
What gets installed
Workflows and templates are copied into your repo. There is no workflow_call to a private host—everything runs as native Actions in your project.
| Workflow | Purpose |
|---|---|
| sprint-child-creator | Child issues from sprint planning (SPRINT - title) |
| auto-close-sprint | Burn-down, sprint health, auto-close at 100% |
| notify-release-approver | Ping approver when a production release issue opens |
| authorize-deployment | Dual approval (release + QA) → ready-for-deploy |
| auto-assign-qa | Assign QA on qa / qa-request |
| telegram-issues | Optional Telegram alerts |
| setup-labels | One-time label creation via Actions |
After install
- Run Setup Labels from the Actions tab (or use
--with-labels). - Set repository variables:
RELEASE_APPROVER,QA_APPROVER,QA_ASSIGNEES(comma-separated). - Optionally add
TELEGRAM_BOT_TOKENandTELEGRAM_CHAT_IDfor notifications.
Use the Sprint Planning template with a title like SPRINT - Sprint 12; list one feature per line under Sprint Features. Child issues link with Parent Sprint: #N.