Release build: copy the release into the plugin's SVN trunk when the plugin has one #56

Summary

After build:release finishes, check whether the plugin has a WordPress.org SVN working copy. If it does, copy the built release contents into its trunk/ folder and stop. No svn add, no svn commit, no tagging: the maintainer runs the rest by hand as today.

Behaviour

• Detect: a local SVN working copy for the plugin slug (path configurable; default ~/Sites/svn/<slug>). No working copy: do nothing and say so.
• Copy: trunk/ becomes exactly the release contents (the files that went into the zip). Files the release no longer carries are deleted from trunk/, except .svn/.
• Report: print the trunk path and a file count. Stop.
• Never run svn commit. Never touch tags/ or assets/.

Ordering

Do this AFTER every plugin is on the feature/gulp5-update branch of this repo. Moving the plugins first avoids building the step twice.

Note

purothemes/plugin-build has a fuller publish-wporg.mjs (stages trunk, tags and assets in a working copy, dry run by default, never commits). It needs a build-config.mjs in the plugin. Worth a look when this step is built, but the step above is the one wanted now.