-
Notifications
You must be signed in to change notification settings - Fork 15.3k
Document how our documentation works #50464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document how our documentation works #50464
Conversation
We still have few todos:
But this one generally describes the flows that we will have once this is complete. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice explanation :)
a30e95e
to
2cdfb1a
Compare
I also added description on how to manually do the same without GitHub Actions. |
2cdfb1a
to
8c28e6c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is nice!
57ba2fa
to
3ba6c6e
Compare
This is high-level description of the architecture and workflows of our documentation building and publishing.
3ba6c6e
to
fd7dae2
Compare
Updated latest comments @eladkal |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool!
This is high-level description of the architecture and workflows of our documentation building and publishing.
This was removed in apache#50464, but we still need to do this step.
This was removed in #50464, but we still need to do this step.
This is high-level description of the architecture and workflows of our documentation building and publishing.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in airflow-core/newsfragments.