-
Notifications
You must be signed in to change notification settings - Fork 815
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
CLI: Add readme to 'jetpack release' #21418
Conversation
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. |
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.
Simple enough. The inline comment on line 74 needs attention; the other you can ignore if you intended the double-spacing.
tools/cli/commands/release.js
Outdated
// Check if we're working with a beta version. | ||
if ( ! argv.devRelease && typeof argv.beta === 'undefined' ) { | ||
// Check if we're working with a beta version and only if generating changlog. | ||
if ( ! argv.devRelease && typeof argv.beta === 'undefined' && argv.script === 'changelog' ) { |
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 doesn't work too well for interactive mode, as argv.script will be unset until you make the call to promptForScript() just after this.
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.
changed the order of the prompts, which seems like a simple enough workaround here.
Looks good to go, other than needing a master merge. |
* master: Releases: start 10.3-a.4 cycle (#21454) Atomic Release: prepare changelogs for today's release (#21453) Connection: fixing the bug with connect button not appearing for secondary users (#21450) CLI: Add readme to 'jetpack release' (#21418) Update handling and setting CCPA related cookies (#21337) Publicize: do not disable toggle connection control when RePublicize is enabled (#21373) External Media: Add bottom padding to Google Photos modal (#21201) Blog Subscription Widget: deprecate widget and transform to block (#21184)
# By Jeremy Herve (2) and others # Via GitHub * master: Releases: start 10.3-a.4 cycle (#21454) Atomic Release: prepare changelogs for today's release (#21453) Connection: fixing the bug with connect button not appearing for secondary users (#21450) CLI: Add readme to 'jetpack release' (#21418) Update handling and setting CCPA related cookies (#21337) Publicize: do not disable toggle connection control when RePublicize is enabled (#21373) External Media: Add bottom padding to Google Photos modal (#21201) Blog Subscription Widget: deprecate widget and transform to block (#21184) # Conflicts: # projects/plugins/boost/tests/e2e/package.json
Changes proposed in this Pull Request:
Adds the
tools/plugin-changelog-to-readme.sh
to the CLI.Jetpack product discussion
#21160
Does this pull request change what data or activity we track or use?
No
Testing instructions:
jetpack release <project> changelog
and the CHANGELOG.md has been generated, follow the instructions to runjetpack release <project> readme