Automatically deploy a WordPress plugin from local git repo to the WordPress Plugin Repostiory (SVN).
Switch branches/tags
Nothing to show
Clone or download
Latest commit 249076a May 30, 2018
Permalink
Failed to load latest commit information.
LICENSE.md Clarify licensing Sep 11, 2017
README.md Docs: Tweak the process / steps list Nov 30, 2017
deploy.sh Revert "Avoid error if xargs is empty" May 30, 2018

README.md

WordPress Plugin Directory Deployment Script

Deploys a WordPress plugin from a local Git repo to the WordPress Plugin Repostiory (SVN).

Steps

These are the steps that the script takes:

  1. Asks for plugin slug.
  2. Asks for local plugin directory.
  3. Checks local plugin directory exists.
  4. Asks for main plugin file name.
  5. Checks main plugin file exists.
  6. Checks readme.txt version matches main plugin file version.
  7. Asks for temporary SVN checkout path.
  8. Asks for remote SVN repo URL.
  9. Asks for SVN username.
  10. Asks if input is correct, and gives chance to abort.
  11. Checks if Git tag exists for version number (must match exactly).
  12. Does checkout of SVN repo.
  13. Sets SVN ignore on some GitHub-related files.
  14. Exports HEAD of master from Git to the trunk of SVN.
  15. Initialises and updates any git submodules.
  16. Moves /trunk/assets up to /assets.
  17. Moves into /trunk, and does an SVN commit.
  18. Moves into /assets, and does an SVN commit.
  19. Copies /trunk into /tags/{version}, and does an SVN commit.
  20. Deletes temporary local SVN checkout.

Install

  1. In your terminal, cd into the directory which contains subdirectories for each of your plugins. i.e. on a local install of WordPress, this will probably be wp-content/plugins. Then git clone https://github.com/GaryJones/wordpress-plugin-git-flow-svn-deploy.git . to clone the deploy script locally.
  2. Ensure that the shell script is executable. In Mac / Unix, run chmod +x deploy.sh.
  3. Run the script with sh deploy.sh. You can also double-click it in Finder / Explorer to start it.
  4. You'll now be guided through a set of questions.

I prefer to keep this script in the root of my projects directory. Each project directory is named as the plugin slug, as is the corresponding GitHub repo. To use, just call the script, enter the plugin slug, confirm or amend default suggestions, and sit back as the code is sent to SVN and git repos including tags. The commit messages here are hard-coded for consistency.

Credits

At one point, well over 90% of this script was written by others:

There has been a significant amount of changes since then though.

License

This package was created at a time when the above credited repositories had no license. For any amendements done since then, the code is licensed under MIT. For the original work, contact the previous authors.