Improve processes of re-publishing docs #60139
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We have been using rather brittle approach to re-publish docs when we had to apply some changes to the released documentation (such as formatting changes or typo fixes). We had to remember about those cherry-picks to apply them again in case of re-re-publish and of course - we forgot. This PR adds a better process for that that can be followed by the release manager easily - and such re-publishing of the docs will be tracked in a new `TAG-docs` branch that we should create and release the documentation from - those branches will track any changes already applied and any re-re-re*-publishing will be based on the previous re-re*publishing.
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
kaxil
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
kaxil
approved these changes
Jan 5, 2026
ephraimbuddy
approved these changes
Jan 5, 2026
jscheffl
approved these changes
Jan 5, 2026
bugraoz93
approved these changes
Jan 5, 2026
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 9fba01e v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
chirodip98
pushed a commit
to chirodip98/airflow-contrib
that referenced
this pull request
Jan 9, 2026
We have been using rather brittle approach to re-publish docs when we had to apply some changes to the released documentation (such as formatting changes or typo fixes). We had to remember about those cherry-picks to apply them again in case of re-re-publish and of course - we forgot. This PR adds a better process for that that can be followed by the release manager easily - and such re-publishing of the docs will be tracked in a new `TAG-docs` branch that we should create and release the documentation from - those branches will track any changes already applied and any re-re-re*-publishing will be based on the previous re-re*publishing.
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
We have been using rather brittle approach to re-publish docs when we had to apply some changes to the released documentation (such as formatting changes or typo fixes). We had to remember about those cherry-picks to apply them again in case of re-re-publish and of course - we forgot. This PR adds a better process for that that can be followed by the release manager easily - and such re-publishing of the docs will be tracked in a new `TAG-docs` branch that we should create and release the documentation from - those branches will track any changes already applied and any re-re-re*-publishing will be based on the previous re-re*publishing.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have been using rather brittle approach to re-publish docs when we had to apply some changes to the released documentation (such as formatting changes or typo fixes). We had to remember about those cherry-picks to apply them again in case of re-re-publish and of course - we forgot.
This PR adds a better process for that that can be followed by the release manager easily - and such re-publishing of the docs will be tracked in a new
TAG-docsbranch that we should create and release the documentation from - those branches will track any changes already applied and any re-re-re*-publishing will be based on the previous re-re*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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.