Move Breeze documentation to inside Breeze and split it. #36936
Merged
Conversation
This file contains 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
potiuk
requested review from
ferruzzi,
pankajkoti,
eladkal,
ephraimbuddy,
dstandish and
jedcunningham
and removed request for
ashb and
jedcunningham
potiuk
force-pushed
the
split-breeze-docs
branch
2 times, most recently
from
87f1dad to
01f2460
Compare
potiuk
force-pushed
the
split-breeze-docs
branch
2 times, most recently
from
c4ec481 to
f1a5b75
Compare
pankajkoti
approved these changes
Jan 21, 2024
potiuk
force-pushed
the
split-breeze-docs
branch
from
f1a5b75 to
80140e5
Compare
The BREEZE.rst document became enormous - enough for it to stop being rendered by GitHub. This change splits it into multiple smaller documents - each focusing on a specific aspect of Breeze, making it possible by the user to focus on only that aspect that the user is interested at. We also add nice index that guides the user to know about all the aspects of Breeze.
potiuk
force-pushed
the
split-breeze-docs
branch
from
80140e5 to
8713ecf
Compare
potiuk
requested review from
ryanahamilton,
bbovenzi and
pierrejeambrun
as code owners
|
That was a big one, thanks for that. |
potiuk
added a commit
that referenced
this pull request
Jan 23, 2024
Following #36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
that referenced
this pull request
Jan 24, 2024
Following #36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jan 25, 2024
Following apache#36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
that referenced
this pull request
Jan 25, 2024
Following #36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
that referenced
this pull request
Jan 26, 2024
Following #36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
that referenced
this pull request
Jan 26, 2024
Following #36936 and the fact that GitHub stopped rendering big .rst files, we also split CONTRIBUTING.rst into multiplet files. It will be much easier to follow and it will render in GitHub.
potiuk
added a commit
to potiuk/airflow
that referenced
this pull request
Jan 27, 2024
This PR moves the documentation of CI of ours to inside Breeze doc folder and splits the documentation in separate docs / chapters following similar changes done for Breeze docs apache#36936 and the contributing docs apache#36969.
potiuk
added a commit
that referenced
this pull request
Jan 27, 2024
potiuk
added a commit
that referenced
this pull request
Feb 7, 2024
The BREEZE.rst document became enormous - enough for it to stop being rendered by GitHub. This change splits it into multiple smaller documents - each focusing on a specific aspect of Breeze, making it possible by the user to focus on only that aspect that the user is interested at. We also add nice index that guides the user to know about all the aspects of Breeze. (cherry picked from commit 4f48e3f)
potiuk
added a commit
that referenced
this pull request
Feb 7, 2024
potiuk
added
the
changelog:skip
ephraimbuddy
pushed a commit
that referenced
this pull request
Feb 22, 2024
The BREEZE.rst document became enormous - enough for it to stop being rendered by GitHub. This change splits it into multiple smaller documents - each focusing on a specific aspect of Breeze, making it possible by the user to focus on only that aspect that the user is interested at. We also add nice index that guides the user to know about all the aspects of Breeze. (cherry picked from commit 4f48e3f)
ephraimbuddy
pushed a commit
that referenced
this pull request
Feb 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 BREEZE.rst document became enormous - enough for it to stop being rendered by GitHub. This change splits it into multiple smaller documents - each focusing on a specific aspect of Breeze, making it possible by the user to focus on only that aspect that the user is interested at.
We also add nice index that guides the user to know about all the aspects of Breeze.
^ 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.