In reply to Jason Lemieux.

People have been struggling to develop on Github and deploy to WordPress.org SVN plugin repository for years. There's been lots of talk with Otto/Samuel Wood about adding Github integration to WordPress.org's SVN here on the tavern, allowing us Github users/WordPress plugin authors to simply point a recent Github version at our WordPress repository and do an instant update.

Ship does work. I just tested it. Ship though is a security nightmare as it grabs access to private repositories in Github as well as public ones as well as full access to your WordPress.org credentials. Deployer is a similar service with similar security issues. Workaround for Github would be to use a dummy user who only has access to your public repositories.

We've coded a WordPress Github to WPSVN plugin in-house which also deploys from Github to WordPress SVN without the same security concerns (passwords only go into your own WordPress site where you have that we are a bit worried about releasing (support nightmare). There are also some paid services doing something similar but WP Pusher does not seem to cover the Github to WordPress SVN trail (they could add it easily enough).

Of course, it would be much, much easier if WordPress.org would just code and enable this feature (one way deployment from Github to WordPress SVN. Ironically Github was recently raked over the coals for being unresponsive to open source project maintainers. Hope is the last thing every lost (Italian proverb).