-
Notifications
You must be signed in to change notification settings - Fork 368
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
Automate Release (Core) #2574
Automate Release (Core) #2574
Conversation
This reverts commit 8ae6bc4.
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 looking good!
I added some comments after reading the code a bit.
Thanks!
.github/workflows/create-release.yml
Outdated
node scripts/create-release.mjs wp-job-manager ${{ github.event.number }} | ||
unzip -q wp-job-manager.zip | ||
- name: Deploy to WordPress.org | ||
uses: 10up/action-wordpress-plugin-deploy@stable |
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 think it would be cool to use a fork inside the Automattic
org for this.
Just to avoid possible security issues.
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.
10up is a pretty reputable company and an Automattic partner, so I think it should be safe enough / not worth maintaining a fork.
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.
Is @stable the latest version? Would it be possible to at least use a specific version?
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.
Pinned this down to a commit hash in e1cf715
console.log( `-----------------------------` ); | ||
console.log( `Pull requests to include (milestone ${ newVersion }):` ); | ||
|
||
execSync( ghPrs, { stdio: 'inherit' } ); |
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.
Maybe I miss something but I think this doesn't do anything
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 one should just output the list of PRs directly to the console.
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.
Good stuff! I think I found a couple of minor issues.
Changes proposed in this Pull Request
npm run release <version>
commandrelease/*
branch, that writes the final changelog entry, creates and tags a new release on GH, then deploys it to WordPress.orgTesting instructions
Usage docs
gh auth login
the first time to set it up