Delivery¶
Source: hooks/ways/softwaredev/delivery/delivery.md
Frontmatter
| Field | Value |
|---|---|
description |
Shipping code — commits, pull requests, releases, migrations, and the path from local changes to production |
vocabulary |
ship deliver deploy release commit push merge pull request pr land code review changelog version tag branch workflow ci cd pipeline promote stage production |
refire |
0.15 |
scope |
agent, subagent |
Before ad-hoc commands, check make help. If the project has a Makefile, it likely has make release, make dist, make deploy, or similar targets that encode the project's actual publishing workflow. Use those.
The children of this way cover each step from a local change to production:
| Stage | Way |
|---|---|
| Commits, messages | delivery/commits |
| PRs, issues, review, merge strategy | delivery/github |
| Jira tickets and Confluence pages | delivery/atlassian |
| Landing an increment — review gate → merge → cleanup | delivery/merge |
| Releases, tagging, publishing | delivery/release |
| Deploying: the account behind a push, proof the live build changed | delivery/deploy |
| Patch creation | delivery/patches |
| Implementation planning | delivery/implement |
| Readiness of an area before changing it | delivery/groundwork |
Deploying a schema migration is a delivery step. Designing, numbering, consolidating and writing idempotent migrations is covered in data/migrations.
See Also¶
- delivery/commits(softwaredev) — commit structure and messages
- delivery/github(softwaredev) — PR workflow
- delivery/merge(softwaredev) — the review gate and landing an increment
- delivery/implement(softwaredev) — implementation planning
- delivery/groundwork(softwaredev) — build, verify, deliver, recover before adding primitives
- data/migrations(data) — designing, numbering and consolidating schema migrations
- delivery/atlassian(softwaredev) — Jira transitions and Confluence pages through the API
- delivery/deploy(softwaredev) — the right account before a push, and proof the live build changed