Bring back limits on branches/tags builds in Airlfow repo#22855
Merged
potiuk merged 1 commit intoapache:mainfrom Apr 8, 2022
Merged
Bring back limits on branches/tags builds in Airlfow repo#22855potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
The change apache#22542 accidentally removed limit on branches that trigger direct push workflows in CI. Currently the builds are also triggered when a new TAG is pushed not only when new branch is created and this is quite too much especially when we push multiple tags for providers :(
Member
Author
|
Ups. Few 10s of credits burned when I pushed 10 tags for providers yesterday ;) |
ashb
approved these changes
Apr 8, 2022
github-actions
bot
added
the
full tests needed
|
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. |
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
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.
The change #22542 accidentally removed limit on branches
that trigger direct push workflows in CI.
Currently the builds are also triggered when a new TAG is pushed
not only when new branch is created and this is quite too much
especially when we push multiple tags for providers :(
^ 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 UPDATING.md.