[GitHub] [airflow] ashb commented on issue #11423: Separate out documentation building and publishing per provider

[GitBox <gi...@apache.org>]

ashb commented on issue #11423:
URL: https://github.com/apache/airflow/issues/11423#issuecomment-731104247


   Sounds great!
   
   Another option might be to publish it as a Release on Github, and then we could install it as
   
   ```
   pip install https://github.com/apache/airflow-site/releases-download/1.0.0/apache_airflow_docs_theme-1.0.0-py3-none-any.whl```
   ```
   
   (To test this I uploaded the artifacts to 2.0.0b3 on Airflow: https://github.com/apache/airflow/releases/tag/2.0.0b3)
   
   The advantage of using Github is Actions already has credentials to create releases (I think?) and we then dont need to manage keys for S3. Disadvantage is that we could only point at specific releases, and couldn't do `airflow-docs-theme>=1.2.3` to instance.


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

For queries about this service, please contact Infrastructure at:
users@infra.apache.org