potiuk commented on code in PR #51153:
URL: https://github.com/apache/airflow/pull/51153#discussion_r2123991909
##########
dev/breeze/src/airflow_breeze/commands/developer_commands.py:
##########
@@ -1153,6 +1153,35 @@ def autogenerate(
fix_ownership_using_docker()
+@main.command(name="build-task-sdk-docs", help="Build the Apache Airflow Task
Execution SDK documentation.")
Review Comment:
Question: is there a particular reason why we want to have a separate
command here rather than using the same mechanisms we already use for other
distributions?
After the refactoring and extraction two months ago, it should be rather
easy to simply use the same mechanisms as for example "airflow-core" users -
where all the common code is in "devel-common" and things liike `uv run --group
docs build-docs --autobuild`
This includes generation of the the docs in `generated` folder where they
are later published using "publish-docs" command to S3. I have a feeling that
simply adding `task-sdk` a another documentation module would be simply easier
when it comes to all the "auxiliary" steps of releasing and publishing.
I am happy to give the right pointers if needed.
--
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: commits-unsubscr...@airflow.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
