Update documentation about folders in Breeze #26559
Merged
potiuk merged 1 commit intoapache:mainfrom Sep 21, 2022
Merged
Conversation
potiuk
requested review from
ashb,
jedcunningham and
mik-laj
as code owners
potiuk
force-pushed
the
fix-dags-breeze-documentation
branch
from
cb4b37b to
1f68656
Compare
potiuk
changed the title
This documentation was partially out-dated - particularly about dag folders mounting (it was updated in some places but not updated in other).
potiuk
force-pushed
the
fix-dags-breeze-documentation
branch
from
1f68656 to
0390dd9
Compare
dstandish
approved these changes
Sep 21, 2022
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.
This documentation was partially out-dated - particularly about
dag folders mounting (it was updated in some places but not
updated in other).
^ 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.