Remove breeze help marker from breeze docs#11572
Closed
feluelle wants to merge 1 commit intoapache:masterfrom
Closed
Remove breeze help marker from breeze docs#11572feluelle wants to merge 1 commit intoapache:masterfrom
feluelle wants to merge 1 commit intoapache:masterfrom
Conversation
potiuk
approved these changes
Oct 16, 2020
Member
Author
|
@potiuk This is not a bug. The marker are required in the final docs. I don't know why but I in the previous PR I thought the |
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 breeze helper marker which is intended to tell the automated breeze script (which builds the docs) where to start and to end was still in the breeze docs.
^ 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.