Open
Conversation
See 10up/action-wordpress-plugin-deploy. `SLUG` included as the GitHub repo slug and the slug on wordpress.org are different.
sjinks
force-pushed
the
ci-deploy-to-wporg
branch
from
cf80299 to
d567588
Compare
|
Kudos, SonarCloud Quality Gate passed!
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To keep code in sync between different sources, we can have tags made in Git and pushed to GitHub, automatically make a push to the WordPress.org tag and trunk directories.
See https://github.com/10up/action-wordpress-plugin-deploy.
SLUGincluded as the GitHub repo slug and the slug on wordpress.org are different.Doesn't appear to be a build process for this repo, so I've removed that step.
A SVN committer's SVN password and username will need to be added to this repo's settings for it to work. The plugin doesn't have
Automatticas a committer.