docs-workflow

You can automate documentation updates for Grafana Tempo PRs by invoking a workflow that coordinates gap analysis, document generation, and quality review across main or release branches, producing PR-to-doc mappings to ensure changes are captured before merging.

The best way to check for documentation gaps is using a three-step pipeline that identifies missing docs, generates or updates content, and validates quality, ensuring PR changes are fully documented and reviewed before merge.

Yes, you can generate PR documentation for specific release branches like release-2.x. The workflow accepts a target branch parameter to align documentation generation and validation with the correct release context.

Yes, the documentation workflow supports multiple PR numbers at once. You provide one or more PR numbers and a target branch, and the workflow automates gap analysis, writing, and review for each PR.

The PR documentation review process works by applying a three-step pipeline that checks for gaps, writes or updates docs, and performs a quality review, culminating in prompts for final review decisions and PR-to-doc mappings.