[AIRFLOW-XXXX] Consistency fixes in new documentation #7207
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
kaxil
reviewed
Jan 19, 2020
kaxil
reviewed
Jan 19, 2020
turbaszek
reviewed
Jan 19, 2020
|
Mergeable fails :) ❌ Must include description for the PR |
mik-laj
approved these changes
Jan 25, 2020
potiuk
force-pushed
the
AIRFLOW-XXXX-consistency-fixes-in-new-documentation
branch
from
2787ead
to
2cf0423
Compare
potiuk
added a commit
that referenced
this pull request
Feb 2, 2020
Co-authored-by: efedotova <[email protected]> (cherry picked from commit 58cc390)
kaxil
pushed a commit
that referenced
this pull request
Feb 3, 2020
Co-authored-by: efedotova <[email protected]> (cherry picked from commit 58cc390)
galuszkak
pushed a commit
to FlyrInc/apache-airflow
that referenced
this pull request
Mar 5, 2020
Co-authored-by: efedotova <[email protected]>
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.
Issue link:
Document only change, no JIRA issueMake sure to mark the boxes below before creating PR: [x]
[AIRFLOW-NNNN]. AIRFLOW-NNNN = JIRA ID** For document-only changes commit message can start with
[AIRFLOW-XXXX].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.
Read the Pull Request Guidelines for more information.