About Deployer

Deployer is a tiny web service that allows WordPress plugin developers to do their development on GitHub and automatically publishes the changes to WordPress.org Plugin Directory.

No more need to waste time figuring out the Subversion versioning system. Just tag a new verson on the GitHub version on GitHub and it will be relased on WordPress.org.

Deployer also handles updates to the readme.txt file and the assets directory.


No More SVN

SVN was a great thing 10 years ago, but now nobody really uses it, except to publish plugins to WP.org. If you want to get of that last part, Deployer will help you.


Publishing to WP.org is handled automatically. You just have to tag a new release on GitHub and it will apear on WP.org.


No WP.org or GitHub credentials are required or stored. The only place where you have to trust Deployer, is allowing a dedicated deployer WP.org user as a commiter to your plugin.


Deployer is, and always will be free for WordPress plugin developers. Period.


Seravo has stepped up to sponsor Deployer. A big thanks to them!


Since Deployer was started in 2015, 1607 plugins have been registered to the service.


For Deployer to work correctly, your GitHub repository has to follow several requirments. It has to have a master branch, where all new releases will be tagged. Optionally it should also have a assets branch, if you want Deployer to handle the assets directory on WP.org. You should also use semantic versioning and tag your releases with version numbers.

Publish a release

In your git repo, run git tag 1.0.1 and git push origin master --tags. Deployer will dow the rest - it will create a new tag on SVN repo, put your new version there and update the readme.txt in the trunk.

Update readme.txt

Whenever you make changes to readme.txt, and push them to github with git push origin master, Deployer will update your readme.txt on WP.org. You don't even need to tag a new release for this.

Update plugin assets

If your GitHub repository has an assets branch, any commits to it will be synced to WordPress.org's assets directory. You can create an empty branch with git checkout --orphan assets and git rm -rf ., then add your asset files and commit them with git add - A, git commit -m 'Initial commit' and git push origin assets.


Does Deployer support publishing themes to WordPress.org?
No. Theme publishing on WordPress.org has a different process, that is not based on SVN - you have to upload .zip files there.

Can Deployer submit a new plugin to WordPress.org?
No. You have to manually submit your plugin here for review. Deployer only works with plugins that already have their WordPress.org site.

Can Deployer convert from readme.md to readme.txt
No. WordPress uses a custom format for their readme.txt file. If you want your plugin to look nice on both GitHub and WordPress.org, you have to have both a readme.md (in Markdown, for GitHub) and readme.txt (for WordPress.org) files.


There will be no more bugfixes to this system and deployer.seravo.com will be completely shut down and stop working on October 1st 2020.

We recommend all WordPress plugin developers migrate to using the new Github Actions based system instead.