-
Notifications
You must be signed in to change notification settings - Fork 61
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
[CMS-1033] add action for building tags and deploying to wp.org #551
Conversation
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.
LGTM after the release date is updated.
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.
Mostly quality of life improvements unrelated to this PR specifically. I am curious about the -dev
suffix and whether that will get stripped in the release process.
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.
🚢
* Add .wordpress-org directory * Update .distignore * Correct version in package.json, set version to -dev * clean up distignore - target only files in repo * Add GH action workflows * Also composer install in action * Add CONTRIBUTING.md file, correct GH action file extension * Add wp before .org for clarity * Set version to 2.3.4 * Update to contrib.md * One more update to contributing.md * ignore contrib.md * Update release, set to dev version for testing new CI * Update Setup step to allow for -dev version tags * update legacy docs
* Add .wordpress-org directory * Update .distignore * Correct version in package.json, set version to -dev * clean up distignore - target only files in repo * Add GH action workflows * Also composer install in action * Add CONTRIBUTING.md file, correct GH action file extension * Add wp before .org for clarity * Set version to 2.3.4 * Update to contrib.md * One more update to contributing.md * ignore contrib.md * Update release, set to dev version for testing new CI * Update Setup step to allow for -dev version tags * update legacy docs
No description provided.