-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fix changelog creation script #541
Conversation
The directory changes follows the guidelines in the docs: https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/#where-do-i-put-my-files
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.
Thank you for fixing this! It tests well for me. Running RELEASE_TYPE=major npm run update-version
, I see the commits from this branch, formatted as expected:
(The screenshot cuts off the bottom, the last line is "* Add text domain to translation target (#499)".)
I see the screenshot changes are in line with what's described in the plugin docs here, so these look fine too.
I think this is good to bring in 👍
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 also working well for me! I tested the update-version
command with major and minor versions.
One question, why change screenshots from jpg to png? The png file size is a lot larger.
No particular reason, that's just the default for when I took them. I've transformed them to jpeg on ef6add0; thanks for spotting! |
Previous Changelogs have come up empty; this PR ensures that the changes since the last tag created are correctly added to the Changelog.
--merge
, since we're not using merge commits.message
instead of the body; GitHub automatically sets the squashed commit to the PR title and adds the number. This should always be available, but will still addbody
as a fallback just in case something is committed without a PR.git
itself to determine the last tag created, instead of using the package.json file.Sample output for v2.0.0 from the updated script:
Testing:
Run
RELEASE_TYPE=major npm run update-version
— Your changelog file will include the commits from this branch, which is fine; when merged, it'll only use the history fromtrunk
.