Automated changelog - use nested headings for feature groups instead of indenting lists #34040
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
5 tasks
|
Size Change: 0 B Total Size: 1.03 MB ℹ️ View Unchanged
|
|
@priethor I think you were keen on this change. When you have a moment let me know if it works for you. |
7 tasks
getdave
deleted the
update/automated-changelog-prefer-headings-over-indentation
branch
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.
Description
In #33719 it was decided that we should prefer nested heading levels over indenting lists for feature groupings.
This PR does that. Here's an example:
Notice how the feature groups (
Block Editor,Widgets Editor...etc) are all headings now and not lists.How has this been tested?
Run
npm run changelog -- --milestone="Gutenberg 11.2" --token=YOUR_GITHUB_PERSONAL_ACCESS_TOKEN.Check the output uses nested headings not nested lists for feature groups.
Screenshots
Types of changes
New feature (non-breaking change which adds functionality)
Checklist:
*.native.jsfiles for terms that need renaming or removal).