-
Notifications
You must be signed in to change notification settings - Fork 97
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
Add generate-pending-release-diffs command #1227
Add generate-pending-release-diffs command #1227
Conversation
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. |
It would have been required as part of #1061. Great that it has been added by @westonruter 🎉 |
Current output:
|
@thelovekesh I see the |
To ensure that we're only including the expected files when we do releases, it's important to review a diff of the changes for each plugin prior to doing a release. This PR introduces a
generate-pending-release-diffs
command to facilitate this.See example output on #1225 (comment)
You can invoke via:
And then the contents can be pasted into a GitHub comment for review. Note the
--silent
arg tonpm run
omits this output:Or you can just directly invoke
./bin/generate-pending-release-diffs.sh
.On MacOS, you can put the output directly onto the clipboard via:
./bin/generate-pending-release-diffs.sh | pbcopy
On Linux, there are equivalent commands.