Lohith625 opened a new pull request, #60566: URL: https://github.com/apache/airflow/pull/60566
<!-- Thank you for contributing! Please provide above a brief description of the changes made in this pull request. Write a good git commit message following this guide: http://chris.beams.io/posts/git-commit/ Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping (in general) for the review if you do not see reaction for a few days (72 Hours is the minimum reaction time you can expect from volunteers) - we sometimes miss notifications. In case of an existing issue, reference it using one of the following: * closes: #ISSUE * related: #ISSUE --> --- ##### Was generative AI tooling used to co-author this PR? <!-- If generative AI tooling has been used in the process of authoring this PR, please change below checkbox to `[X]` followed by the name of the tool, uncomment the "Generated-by". --> - [X] Yes Generated-by: ChatGPT following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --- This PR clarifies the relationship between Airflow’s execution-time template context and the Task SDK Context object. ### What is changed - Added a short explanatory note in the templates reference to explain that the listed variables are provided via the execution-time context - Added a cross-reference to airflow.sdk.Context for users working with the Task SDK ### Why this is needed The Context API documentation does not currently explain how it relates to the template context described in the templates reference, which can be confusing for users moving between templating and Task SDK usage. This change improves discoverability without duplicating documentation. Related: #60476 -- 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]
