Àpèjúwe
Easily trigger a GitHub Actions workflow from your WordPress site whenever a post is created, updated, or deleted. Perfect for headless WordPress setups to automate frontend deployments and keep your site in sync.
- Triggers a GitHub Actions workflow on post save or delete
- Manual deploy/reset options from the settings page
- Securely stores your GitHub token
- Works with any post type
External services
This plugin connects to the GitHub API to trigger GitHub Actions workflows. This service is required to automatically deploy your site when content changes.
The plugin sends the following data to GitHubÌtumọ̀ Yorùbá: ’s API:
Ìtumọ̀ Yorùbá: – Repository information (user/repo format)
Ìtumọ̀ Yorùbá: – Workflow filename
Ìtumọ̀ Yorùbá: – Branch reference (default: main)
Ìtumọ̀ Yorùbá: – GitHub personal access token for authentication
This data is sent every time a post is created, updated, or deleted (when the post status is ‘publish’). The GitHub token is stored securely in your WordPress database and is never displayed in plain text.
This service is provided by GitHub, Inc.:
Ìtumọ̀ Yorùbá: – Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
Ìtumọ̀ Yorùbá: – Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement
Ìgbéwọlẹ̀
- Upload the plugin files to the
/wp-content/plugins/wc-github-deployerdirectory, or install the plugin through the WordPress plugins screen directly. - Activate the plugin through the ‘Plugins’ screen in WordPress.
- Create a GitHub Personal Access Token in your GitHub account with ‘repo’ permissions for the target repository.
- Go to ‘Settings’ > ‘GitHub Deploy’ and configure your GitHub token, repository, workflow filename, and branch.
- Save changes. The plugin will now trigger your workflow on post save or delete.
FAQ
-
Is my GitHub token safe?
-
Yes, your token is stored securely in the WordPress options table and never displayed in plain text.
-
Can I trigger the deploy manually?
-
Yes, there is a button on the settings page to manually trigger the deploy.
-
Does it work with custom post types?
-
Yes, it works with any post type.
Àwọn àgbéyẹ̀wò
Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.
Àwọn Olùkópa & Olùgbéejáde
“Deploy Trigger for GitHub” 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ópaTúmọ̀ “Deploy Trigger for GitHub” 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.4
- Fixed WordPress.org compliance issues
- Updated text domain to match plugin slug (deploy-trigger-for-github)
- Renamed all functions and options with unique prefix (depltrfo_)
- Added external services documentation for GitHub API
- Improved code structure and naming conventions
1.3
- Improved error handling and logging
- Updated documentation
1.2
- Added reset button to clear plugin data
- Improved code structure and security
1.1
- Added support for post deletion trigger
1.0
- Initial release