Add --overwrite when publishing documentation to S3 #50543
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
Member
Author
|
I found it out when I tried to re-publish amazon and snowflake with |
Member
Author
potiuk
added
the
backport-to-v3-1-test
potiuk
changed the title
When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it.
potiuk
force-pushed
the
add-overwrite-to-publishing-to-s3
branch
from
3f88d95 to
12ad134
Compare
gopidesupavan
approved these changes
May 13, 2025
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker d88bf3f v3-0-testThis should apply the commit to the v3-0-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 |
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
May 14, 2025
…he#50543) When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it. (cherry picked from commit d88bf3f) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
potiuk
added a commit
that referenced
this pull request
May 14, 2025
…) (#50611) When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it. (cherry picked from commit d88bf3f)
kaxil
pushed a commit
that referenced
this pull request
Jun 3, 2025
…) (#50611) When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it. (cherry picked from commit d88bf3f)
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
When we are rerunning the old doc builds, we really want to overwrite existing documentation, there is no point in silently skipping the docs - this is useful for manual pushing because you can make a mistake easily but when you are runnig it in workflow, you run it from a specified tag and the docs are for sure built from this tag so our intention is to override it.
^ 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.