Improve error message when publish-docs ref is a branch not a tag#66250
Merged
Conversation
1 task
jscheffl
approved these changes
May 2, 2026
potiuk
approved these changes
May 2, 2026
potiuk
reviewed
May 2, 2026
ee7eeff to
6bb3a5d
Compare
bugraoz93
approved these changes
May 3, 2026
Contributor
bugraoz93
left a comment
There was a problem hiding this comment.
Looks good! Static checks still failing
vincbeck
approved these changes
May 4, 2026
6bb3a5d to
971ed8d
Compare
potiuk
approved these changes
May 10, 2026
Member
|
Needs rebase @shahar1 |
971ed8d to
bc46b60
Compare
1 task
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 running breeze workflow-run publish-docs with --ref pointing to a docs branch (for example providers/YYYY-MM-DD-docs) and without --skip-tag-validation, the previous error implied the ref did not exist.
Actual problem: ref existed as branch, but command only checked tags.
This PR changes validation flow:
Tests added/updated for:
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot (GPT-5.3-Codex) following the guidelines
Drafted-by: GitHub Copilot (GPT-5.3-Codex) (no human review before posting)