-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changelogs: Standardize sections #58268
Conversation
Size Change: +165 B (+0.01%) Total Size: 1.76 MB
ℹ️ View Unchanged
|
ce85581
to
3e52a6a
Compare
I would bring closer the headlines with available labels for PRs and issues. @priethor, might be the best person to help you bring clarity here. I have a larger change in the release flow that would benefit from the changes you started here. |
3e52a6a
to
c012a63
Compare
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
@@ -46,7 +46,7 @@ function calculateVersionBumpFromChangelog( | |||
let changesDetected = false; | |||
let versionBump = null; | |||
for ( const line of lines ) { | |||
const lineNormalized = line.toLowerCase().trimLeft(); | |||
const lineNormalized = line.toLowerCase().trimStart(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is replacing a deprecated String
method (alias) with its recommended replacement.
6d5e6ca
to
5686e54
Compare
Good spot, I've cleaned up the wrong levels in package changelogs. This also lead me to the root changelog.txt file where I did a fair amount of cleanup and standardization. It would be nice to change that file to an |
Flaky tests detected in 5686e54. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9561113503
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a few suggestions at the end, all of which appear to be formatted correctly.
What?
Improve existing changelog entries to adhere to a more standard format. I've changed all similar names the seem clear to be:
I've updated the documentation as well.
I've also updated the root changelog and the changelog script to use "first-time contributors" (hyphenated) instead of "first time contributors." I understand this is correct, where "first-time" is and adjective.
Should more things be moved to standard names?
Why?
We expect a relatively standard format but nothing enforces it. Using regular sections in CHANGELOGs helps releases go smoothly and keeps changelogs clear.