Repository navigation
Render the HITL review workflow as a Mermaid diagram - #74024
Merged
Merged
Conversation
The sequence diagram was hand-drawn as a fixed-width ASCII `code-block`, which is hard to scan and easy to let drift from the actual control flow. The docs build already ships `sphinxcontrib.mermaid` (used by the provider ERD pages), so render it instead. A single sequence diagram covering both the message exchange and the five-way outcome branch read as more cluttered than the original text, so split it in two: a sequence diagram for the poll/respond exchange, and a flowchart for what the operator does once it reads an action.
kaxil
approved these changes
Oct 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The sequence diagram was hand-drawn as a fixed-width ASCII
code-block, which is hard to scan and easy to let drift from the actual control flow. The docs build already shipssphinxcontrib.mermaid(used by the provider ERD pages), so render it instead.A single sequence diagram covering both the message exchange and the five-way outcome branch read as more cluttered than the original text, so split it in two: a sequence diagram for the poll/respond exchange, and a flowchart for what the operator does once it reads an action.
Before
After
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.