GitHub Action to automatically publish releases to wordpress.org Subversion

[mklasen]

Hey there!

I noticed some discussion on automatically publishing to SVN in #33 (great work btw!) and thought I'd setup a base for this. This is my workflow for the Sympose plugin, found here: https://github.com/conference7/sympose/blob/trunk/.github/workflows/main.yml

SVN username and password will have to be added as secrets to the repository settings. Does need some testing as i'm not sure if and which other changes are necessary.

Configuration file copied from: https://github.com/conference7/sympose/
Action used: https://github.com/10up/action-wordpress-plugin-deploy

How this works:

• By using this workflow, new versions are automatically committed to SVN when a new release is published

Step by step:

1. Commit new code to master branch
2. Go to releases
3. Create new release based on master branch (create new tag, eg: v.1.2)
4. After the release is created, an action is launched
5. When the action is finished, the new release is available in the WordPress repository.

[sun]

Nice! 👍

According to https://github.com/10up/action-wordpress-plugin-deploy#excluding-files-from-deployment we should include a .distignore file in this PR to exclude at minimum /node_modules, possibly more.

Do you know of a command or tool to bump the major/minor/patch version in all the files? (Plugin file header, composer.json, package.json, readme.txt)

[mklasen]

Ah - yes. I've copied over some sample content. Happy to cut it down when the plans for auto-syncing to SVN are more serious. I've also included some more (how to) information in my initial PR message.

[sun]

Unfortunately I think that this is obsolete in the meantime as @dominic-ks already added some GitHub Actions to automate the deployment of releases to wordpress.org. I believe it is using similar actions as proposed here and your contribution might have served as inspiration 🙌