Jasperora commented on code in PR #54618:
URL: https://github.com/apache/airflow/pull/54618#discussion_r2286664002
##########
airflow-core/docs/tutorial/hitl.rst:
##########
@@ -95,6 +117,38 @@ And remember to specify their relationship in the workflow.
:start-after: [START howto_hitl_workflow]
:end-before: [END howto_hitl_workflow]
+.. image:: /img/hitl_branch_selection.png
+ :alt: Demo HITL task instance waiting for branch selection
+
+After the branch is chosen, the workflow will proceed along the selected path.
+
+.. image:: /img/hitl_branch_selected.png
+ :alt: Demo HITL task instance after branch selection
+
+Notifiers
+---------
+
+A notifier is a callback mechanism that allows you to handle HITL events, such
as when a task is waiting for human input, succeeds, or fails.
+The example uses a notifier ``LocalLogNotifier`` that logs messages for
demonstration.
+You can implement your own notifier for different functionalities.
+
+In the example DAG, the notifier is defined as follows:
+
+.. exampleinclude::
/../../providers/standard/src/airflow/providers/standard/example_dags/example_hitl_operator.py
+ :language: python
+ :start-after: [START hitl_notifier]
+ :end-before: [END hitl_notifier]
+
+You can pass a list of notifiers to HITL operators using the ``notifiers``
argument as follows.
+When the operator reaches certain states, the ``notify`` method will be called.
Review Comment:
I use double backticks for `notify` and `context ` since double backtick is
needed for code in RST files.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
