Render changelog sections only if they contain content#40660
Merged
uranusjr merged 1 commit intoapache:mainfrom Jul 9, 2024
Merged
Render changelog sections only if they contain content#40660uranusjr merged 1 commit intoapache:mainfrom
uranusjr merged 1 commit intoapache:mainfrom
Conversation
Contributor
Author
eladkal
approved these changes
Jul 9, 2024
uranusjr
approved these changes
Jul 9, 2024
Member
|
Oh yeah - it makes sense now when we classification of changes is done before generating the docs. Good call @amoghrajesh :) |
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
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
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.
While categorising PRs for providers, if a section didn't have any content, empty headers were rendered. This PR makes that content conditional.
Example output:
^ 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.