-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
First attempt to have CI-controlled process of releasing PROD image #24433
Conversation
cefa3c4
to
27213a5
Compare
27213a5
to
427a6b6
Compare
Hey @jedcunningham @ephraimbuddy - we seem to have the secrets sets (at organisation level but only accesspible to us) so you cannot see them when you query for secrets in repo. Unfortunately, The only way to check the workflow is to merge it (the workflow must be merged in main so that we can run it). |
427a6b6
to
c0ba68b
Compare
:D |
f94d911
to
fadcc09
Compare
fadcc09
to
c58bc0f
Compare
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
…pache#24433) (cherry picked from commit b79790d)
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 newsfragement file, named
{pr_number}.significant.rst
, in newsfragments.