amoghrajesh commented on code in PR #34004:
URL: https://github.com/apache/airflow/pull/34004#discussion_r1314561056


##########
dev/README_RELEASE_PROVIDER_PACKAGES.md:
##########
@@ -366,6 +374,14 @@ breeze build-docs --clean-build \
   ...
 ```
 
+You can also use shorthand names as arguments instead of using the full names
+for airflow providers. Example:
+
+```shell script
+cd "${AIRFLOW_REPO_ROOT}"
+breeze build-docs package1 package2 --clean-build

Review Comment:
   > How does this work for building apache-airflow-providers ?
   I do not think there is a special rule for this. Might need to add one? We 
can follow the instructions above for this too, no need of any args
   
   >Not that now you can remove the build_provider_documentation.sh part from 
the guide. Is this script being used somewhere? If not I guess we can remove it
   
   Yeah only here. I think we can safely remove it.



##########
dev/README_RELEASE_PROVIDER_PACKAGES.md:
##########
@@ -366,6 +374,14 @@ breeze build-docs --clean-build \
   ...
 ```
 
+You can also use shorthand names as arguments instead of using the full names
+for airflow providers. Example:
+
+```shell script
+cd "${AIRFLOW_REPO_ROOT}"
+breeze build-docs package1 package2 --clean-build

Review Comment:
   > How does this work for building apache-airflow-providers ?
   
   I do not think there is a special rule for this. Might need to add one? We 
can follow the instructions above for this too, no need of any args
   
   >Not that now you can remove the build_provider_documentation.sh part from 
the guide. Is this script being used somewhere? If not I guess we can remove it
   
   Yeah only here. I think we can safely remove it.



-- 
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]

Reply via email to