You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently doc publishing is a complex process - it involves checking two repos and copying code between them, just to publish generated code from one repo to the other and then push it so that it can be published. That requires not only to have both repos checked out at the same time locally but also some linking between them and it only works from local machine.
We could get rid of all that completely if we have just one publishing workflow in "airflow" CI. Once we move to "s3" only storage and exposing as website (via #45621), there is no need to copy the files to the separate repo any more, and with #45613 where we can move sphinx airflow theme to the main reapo as well, the whole publishing framework could be done as a set of workflow publishing the docuementation - straight from "airlfow" repository.
The text was updated successfully, but these errors were encountered:
Currently doc publishing is a complex process - it involves checking two repos and copying code between them, just to publish generated code from one repo to the other and then push it so that it can be published. That requires not only to have both repos checked out at the same time locally but also some linking between them and it only works from local machine.
We could get rid of all that completely if we have just one publishing workflow in "airflow" CI. Once we move to "s3" only storage and exposing as website (via #45621), there is no need to copy the files to the separate repo any more, and with #45613 where we can move sphinx airflow theme to the main reapo as well, the whole publishing framework could be done as a set of workflow publishing the docuementation - straight from "airlfow" repository.
The text was updated successfully, but these errors were encountered: