This is an automated email from the ASF dual-hosted git repository.
kaxilnaik pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/v3-1-test by this push:
new 4eecd4d03b5 Fix formatting issue in Deadline Alerts' docs (#55911)
4eecd4d03b5 is described below
commit 4eecd4d03b5833ad1ca36cd7ad77e971e4141e3f
Author: Ramit Kataria <[email protected]>
AuthorDate: Fri Sep 19 16:59:14 2025 -0700
Fix formatting issue in Deadline Alerts' docs (#55911)
Everything between the 2 mentions of the word "Notifier" in the
"Templating and Context" section was being rendered as inline code
because I made the first one plural (with an "s" right after the double
backticks).
I've fixed this by making Notifier render as regular text instead. This
also makes it more consistent with the rest of the doc page.
(cherry picked from commit 5fdd5b66d183e0cdaba4a75bca7c38988f16ab33)
---
airflow-core/docs/howto/deadline-alerts.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/airflow-core/docs/howto/deadline-alerts.rst
b/airflow-core/docs/howto/deadline-alerts.rst
index 33d420e1214..e52fdd6aeb1 100644
--- a/airflow-core/docs/howto/deadline-alerts.rst
+++ b/airflow-core/docs/howto/deadline-alerts.rst
@@ -226,8 +226,8 @@ Templating and Context
^^^^^^^^^^^^^^^^^^^^^^
Currently, a relatively simple version of the Airflow context is passed to
callables and Airflow does not run
-:ref:`concepts:jinja-templating` on the kwargs. However, ``Notifier``s already
run templating with the
-provided context as part of their execution. This means that templating can be
used when using a ``Notifier``
+:ref:`concepts:jinja-templating` on the kwargs. However, Notifiers already run
templating with the
+provided context as part of their execution. This means that templating can be
used when using a Notifier
as long as the variables being templated are included in the simplified
context. This currently includes the
ID and the calculated deadline time of the Deadline Alert as well as the data
included in the ``GET`` REST API
response for Dag Run. Support for more comprehensive context and templating
will be added in future versions.
