Update description of branch creation to include the new Breeze #25155
Conversation
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
The new Breeze has a different place where default branch and constraints branch are kept. When we create a new "release" branch we should update it here as well as in the bash legacy breeze (until the bash breeze has stil some zombies around)
Member
Author
|
I noticed the description of branch creation was not updated with the new Breeze while I was explaining the "default branch" concept to @jedcunningham in #25056 (comment) |
Member
Author
|
We should merge it before 2.4 :) |
jedcunningham
approved these changes
Jul 19, 2022
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
potiuk
added a commit
that referenced
this pull request
Jul 21, 2022
* Update description of branch creation to include the new Breeze The new Breeze has a different place where default branch and constraints branch are kept. When we create a new "release" branch we should update it here as well as in the bash legacy breeze (until the bash breeze has stil some zombies around) (cherry picked from commit 8923e3a)
ephraimbuddy
added
the
changelog:skip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 new Breeze has a different place where default branch and
constraints branch are kept.
When we create a new "release" branch we should update it here
as well as in the bash legacy breeze (until the bash breeze has
stil some zombies around)
^ 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 newsfragments.