GitHub published a detailed example of Agentic Workflows being used for a practical developer-infrastructure problem: keeping product documentation aligned with code changes across repositories.

The case study comes from the Aspire team, which maintains product code in microsoft/aspire and documentation in microsoft/aspire.dev. According to GitHub, Aspire used Agentic Workflows to turn merged product pull requests into draft documentation pull requests that still require review from the relevant subject-matter expert.

The reported result is specific: for Aspire 13.3 and 13.4, the system produced 82 feature-documentation pull requests that merged at a median of 44.8 hours after the related product pull request. GitHub says each was reviewed by the engineer who shipped the feature.

The workflow is not described as an unconstrained agent with broad repository access. GitHub's model uses markdown-defined workflows that compile into locked GitHub Actions files. At runtime, the agent reads the relevant context and emits an intended action, while a separate safe-output handler applies that action through narrower permissions.

That architecture is the most important part of the announcement. It positions agents as event-driven processors inside existing CI systems, with repository permissions, sandboxing, and review gates still doing much of the control work.

For teams testing AI agents in production workflows, the example is a useful benchmark: start with a repetitive, reviewable task, keep the agent away from direct write access, and make the output land where humans already review changes.