sync-docs-release

To automate syncing documentation with a software release, use a workflow that manages git worktrees and pull request lifecycles to apply doc patches safely. This sequences documentation updates before cutting the final release.

Documentation gets out of sync during a release because manual updates often lag behind code changes. Automating the end-to-end workflow ensures a subagent syncs docs to recent commits before the release is published, eliminating manual overhead.

Yes, you need GitHub CLI to automate pull request management for documentation updates. The workflow requires git and GitHub CLI to perform branch management, apply patches, and manage PR lifecycles safely without polluting the default branch.

Git worktree helps land documentation changes safely by isolating branch creation and patch application from the default branch. This ensures documentation updates are applied and reviewed via pull requests without polluting the main codebase.

Yes, you can use subagents to handle release tasks and documentation synchronization. The workflow triggers a configured subagent runner to sync documentation to recent commits and execute subagent-driven release tasks for consistency.

The best way to coordinate documentation updates with code changes is orchestrating an end-to-end sequence that triggers doc synchronization, manages PR merges, and then cuts the release artifact to ensure it contains updated documentation.