Automattic / Automattic/jetpack
Jetpack CLI: Time to add `jetpack release`
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
### Impacted plugin
None / Other
### What
There are a lot of packages/plugins/teams working and releasing in the repo now. We should add a release command to the CLI that acts as a wrapper for the release scripts.
### How
We should start simple, basically just wrapping `tools/changelogger-release.sh [-b] [project]` to kickstart the changelog tool.
From there, we can build out the rest of the tools in the UI. I'm thinking the flow might be something like:
`jetpack release`
- What project are you releasing?
- plugins
- packages
- etc
- Is this a beta release? (y/N)
- What would you like to do?
- Update changelog.md [tools/changelogger-release.sh [-b] [project]]
- maybe run `cd projects/plugins/jetpack && vendor/bin/changelogger write --amend` if it's not a beta.
- Update readme.md (if plugin) [tools/changelogger-release.sh [-b] [project]]
- Create a release branch (if plugin) [ tools/create-release-branch.sh jetpack x.x[-beta]]
Should be enough to bite out to start and iterate on the way.
Contributor guide
Assessment
This issue has not been assessed yet.