-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Add breeze commands for gh workflow docs publish #51036
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
Add breeze commands for gh workflow docs publish #51036
Conversation
|
Still UI option is available to trigger :) |
1b3911a to
1645280
Compare
bugraoz93
left a comment
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.
Looks great! Great addition. Small nit :)
Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
|
@potiuk currently the breeze command has this option |
Backport failed to create: v3-0-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 7bd29f4 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 |
* Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
|
Nice! |
I think it would be better to revert it - make it |
hard time last few days, agree will check this one today. |
|
We run from main right, thought do we need backport? |
Absolutely no worries Pavan. We all have lives :) . I hppe all is fine. |
We will need backport, yes for Airflow docs |
* Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
* Add breeze commands for gh workflow docs publish (#51036) * Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> * Update GH cli bool inputs to convert to string format in breeze and input branch to refresh site and sync s3 to github (#51093) * Update GH cli bool inputs to convert to string format in breeze * Update branch name to airflow-site-archive trigger * DOCS: Remove site-refresh/sync-s3-to-github and Update release documentation instructions (#51259) * Remove refres sit and sync s3 to github docs args * Update release readme files * Update release readme files --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
Yeah all okay :) |
* Add breeze commands for gh workflow docs publish (#51036) * Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> * Update GH cli bool inputs to convert to string format in breeze and input branch to refresh site and sync s3 to github (#51093) * Update GH cli bool inputs to convert to string format in breeze * Update branch name to airflow-site-archive trigger * DOCS: Remove site-refresh/sync-s3-to-github and Update release documentation instructions (#51259) * Remove refres sit and sync s3 to github docs args * Update release readme files * Update release readme files --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
* Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
* Add breeze commands for gh workflow docs publish * Add breeze commands for gh workflow docs publish * Add sync s3 to github workflow trigger * Update dev/breeze/src/airflow_breeze/utils/gh_workflow_utils.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>

Adding gh workflow commands, to breeze to trigger workflows.
At present release managers have to do manually running the workflows on multiple repository. to make it easier, we can chain all the steps and run from local.
All the release managers should have already access to trigger workflows from the local.
When running the below command it does following:
See the documentation for more options.
A sample console log from local(Note: i have used my personal repo ;) :
^ 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.