Take the pain out of WordPress development. Deploy directly from Github and never again copy files over FTP. It works everywhere – even on cheap share
| Author: | WP Pusher (profile at wordpress.org) |
| WordPress version required: | 3.9 |
| WordPress version tested: | 4.1 |
| Plugin version: | 1.0.0 |
| Added to WordPress repository: | 23-12-2014 |
| Last updated: | 11-01-2015
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 100 |
| Rated by: | 2 |
| Plugin URI: | http://wppusher.com |
| Total downloads: | 64 |
 Click to start download |
|
Features
- Install and update your WordPress themes and plugins directly from GitHub
- BitBucket support
- Easy version control of your clients code
- Works everywhere because it hooks in to the WordPress core auto updater
- No Git or SSH needed on the server
PRO features
- Push-to-deploy can automatically trigger updates when whenever you push to GitHub (Coming soon)
- E-mail support
Coming soon
- Support for self-hosted Git repositories like GitLab
- Release notifications in WordPress dashboard - notify clients on updates
Get started
If you already use Git for your projects and your themes and plugins are in their own repositories on GitHub, getting started with WP Pusher is simple and easy. Just go to "New plugin" or "New theme" in the WP Pusher menu and type in the repository for the package: github-username/repository-name
If any of your plugins or themes are in private repositories on GitHub, WP Pusher will need a token to access them. You can read GitHub's guide to application tokens here. Paste in the token at WP Pusher settings page.
Conventions
- Theme stylesheets must be named the same as the repository
- Plugin directories must be named the same as the repository
- GitHub version tags must be numeric, such as '1.0' or '1.0.1', with an optional preceding 'v', such as 'v1.0.1'
- WordPress version tags must be numeric, such as '1.0' or '1.0.1'
Git workflow
The way WP Pusher works, packages (themes and plugins) need to be in their own repositories. If your packages are in their own repositories already, you can safely skip this section. Some developers prefer having their whole WordPress installation under Git, which potentially makes things a bit more complicated. By having all packages in their own repositories, you can easily share code across clients / projects. Since you shouldn’t be editing the core WordPress code, in most cases having the whole project under Git shouldn’t be necessary. However, if for some reason your project require that you have one Git repository for the whole project, you will have to use Git submodules, so that you can still have every package in its own (sub) repository.