Skip to content

Conversation

@gopidesupavan
Copy link
Member

@gopidesupavan gopidesupavan commented Aug 18, 2025

Currently it defaults to main always, even when we run docs publishing from the rc or v3 test branches. We have just an issue where we were not able to run workflow from selected branch due.

The failed workflow:
https://github.com/apache/airflow/actions/runs/17047698357/job/48327631488

This adds option to select branch to select workflow.


^ 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.

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Aug 18, 2025
@kaxil
Copy link
Member

kaxil commented Aug 18, 2025

Worth adding a PR description please :)

@gopidesupavan
Copy link
Member Author

Worth adding a PR description please :)

yeah sorry added now :)

Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@gopidesupavan gopidesupavan force-pushed the update-workflow-commands branch from 4b458ad to 634269e Compare August 18, 2025 20:04
@gopidesupavan
Copy link
Member Author

Failed tests not related to this, i am looking at it now. those failed in CI run aswell .

@gopidesupavan gopidesupavan merged commit b07a2d2 into apache:main Aug 18, 2025
96 of 103 checks passed
@gopidesupavan gopidesupavan deleted the update-workflow-commands branch August 18, 2025 21:32
@github-actions
Copy link

Backport failed to create: v3-0-test. View the failure log Run details

Status Branch Result
v3-0-test Commit Link

You can attempt to backport this manually by running:

cherry_picker b07a2d2 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

@gopidesupavan
Copy link
Member Author

will port it manually now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants