Docs that ship with the code that changed them
AutoDevOps makes documentation a side-effect of shipping code. READMEs, API references, ADRs, and runbooks update in the same PR — reviewable, auditable, and never silently stale.
Doc workflow config
hooks:
post-merge:
- run: doc-updater
targets:
- README.md
- docs/api
- docs/adr
governance:
default: confirm
telemetry:
enabled: trueStale docs are a slow-motion incident
Same workflow as code
Doc updates happen in the commit or PR that changed the behavior. No separate backlog ticket.
Reviewable before merge
Generated docs go through the same approval flow as code changes — not silent background rewrites.
Template-aware generation
Agent context, repo structure, and team templates produce docs that match your existing artifact format.
The docs your team actually depends on
READMEs and onboarding
Setup guides, workflow docs, and getting-started content that stays current with actual project behavior.
API references
Contract-facing docs update automatically when schemas, routes, or integration behavior change.
ADRs, release notes, runbooks
Capture rationale and operational impact while the diff context is still fresh — not weeks later.
Who benefits
Engineering leads
Onboarding docs and runbooks that reflect what actually shipped — not what shipped three sprints ago.
Security teams
Runbooks and incident response docs under the same review flow as code. No ad-hoc wiki edits.
Platform engineers
Templates and policy-enforced workflows so generated docs match your team's existing format and standards.
Stop treating docs as a separate workstream.
Same approval, same telemetry, same deployment controls as the rest of your engineering workflow.