Deployer for Git

Àpèjúwe

The Deployer for Git (and Deployer for Git Pro) are designed for developers who seek to simplify their website changes deployment. This tool seamlessly connects your WordPress site with various git repositories, enabling real-time updates and automated deployments directly from your commits. This plugin makes it easy — no FTP, no zipping files. Supports all popular services.

Àwọn àwòrán ìbòjú

  • Dashboard
  • Install Theme Page
  • Settings page

FAQ

Do I need Git installed on the server?

No. Deployer for Git does not require Git to be installed on the server.

I have shared/cheap hosting, will it work on my server?

Yes, as long as your server runs WordPress, the plugin will work fine.

What git repositories are supported by Deployer For Git?

The plugin supports Bitbucket, GitHub, Gitea, and GitLab repositories.

Is there any way to clear website cache after each deploy?

Yes, itÌtumọ̀ Yorùbá: ’s possible. Plugin supports WP Rocket, WP-Optimize W3 Total Cache, LiteSpeed Cache, WP Super Cache, WP Fastest Cache and Autoptimize.

How does Deployer For Git improve website management?

By automating the deployment process. Once set up, the plugin automatically updates your WordPress instance after each commit of the desired branch to your git repository, eliminating the need for manual file transfers via FTP.

Can I use Deployer For Git for multiple websites?

Yes, the plugin can be used for multiple websites. Each website will require its own setup to connect to the respective git repository.

Is there a cost associated with Deployer For Git?

The PRO version is required if you plan to use the plugin with private repositories.

Does it support WordPress Multisite?

Yes, it does.

Is there any risk of data loss when using Deployer For Git?

The plugin is designed to safely update your website with the latest changes from your git repository. However, as with any deployment tool, it\Ìtumọ̀ Yorùbá: ’s always recommended to have regular backups of your site.

Àwọn àgbéyẹ̀wò

Ọ̀pẹ 2, 2025 1 ìdáhùn
Thank you for creating this! ItÌtumọ̀ Yorùbá: ’s so simple and so perfect for what I need.
Agẹmọ 23, 2025
This is a fantastic plugin for theme or plugin development. It has proven to be helpful for our teamÌtumọ̀ Yorùbá: ’s workflow. The free version functionality is excellent, but the Pro version is worth the upgade. Also the developer of this plugin is very responsive.
Bélú 4, 2024 1 ìdáhùn
IÌtumọ̀ Yorùbá: ’m using it for some time already and it works great, saves me a lot of time to deploy.
Èbìbí 10, 2024
I had a client that has a bit unusual server setup so we had problems setting up GitHub Actions and making them work.The client has paid for the Pro version since our repositories are private.Everything worked like charm Ìtumọ̀ Yorùbá: – after pushing my changes I simply went to wp-admin and clicked a button to pull the changes from GitHub.We have 3 repositories on that website.Then I realized that each repository has a special deployment link, so I created GitHub Action to do a GET request to that URL, and that worked like a charm, even behind the basic auth that the website uses.So now our changes get deployed automatically.Definitely a great and simple solution than setting up the pipelines which always cause problems on different platforms.Good job! EDIT:I found 2 features IÌtumọ̀ Yorùbá: ’d like to see in the next version:- An option to define the folder nameMy GitHub repository is not named the same as IÌtumọ̀ Yorùbá: ’d like the pluginÌtumọ̀ Yorùbá: ’s folder to be named.Currently, thereÌtumọ̀ Yorùbá: ’s no way to influence that.- The name of the last commit included in the log fileItÌtumọ̀ Yorùbá: ’s rather hard to quickly confirm that all my last commits got deployed.Currently, itÌtumọ̀ Yorùbá: ’s almost 1am where I am, but the server is set to a different time zone so itÌtumọ̀ Yorùbá: ’s still yesterday.When I checked the logs, the date of the last entry was 1 day behind my current date.The reason I even checked the logs is because the browser has hashed my CSS so I couldnÌtumọ̀ Yorùbá: ’t see all the changes.Having the last commit message would help quickly confirming that everything was deployed properly.
Ka gbogbo àwọn àgbéyẹ̀wò 12

Àwọn Olùkópa & Olùgbéejáde

“Deployer for Git” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

Àwọn Olùkópa

Túmọ̀ “Deployer for Git” sí èdè rẹ.

Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?

Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.

Àkọsílẹ̀ àwọn àyípadà

1.0.11

  • Added ability to unlink plugin or theme
  • Flush cache: Breeze support added
  • UI/UX updates

1.0.10

  • Added ability to edit package credentials
  • Compatibility updates

1.0.9

  • Bitbucket “App Passwords” support added
  • Small UI/UX updates
  • Compatibility updates

1.0.8

  • Compatibility updates

1.0.7

  • GitHub “Fine-grained personal access tokens” support added

1.0.6

  • Compatibility updates

1.0.5

  • Support for self-hosted Gitea repositories

1.0.4

  • GitLab groups support added

1.0.3

  • Experimental support for self-hosted GitLab repositories

1.0.2

  • Multisite support added

1.0.1

  • Minor interface improvements
  • Plugin is localizable now
  • Ukrainian translation added

1.0

  • Initial release