Facundo

<p>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.</p>
<ul>
<li>Triggers a GitHub Actions workflow on post save or delete</li>
<li>Manual deploy/reset options from the settings page</li>
<li>Securely stores your GitHub token</li>
<li>Works with any post type</li>
</ul>
<h3>External services</h3>
<p>This plugin connects to the GitHub API to trigger GitHub Actions workflows. This service is required to automatically deploy your site when content changes.</p>
<p>The plugin sends the following data to GitHub’s API:<br />
– Repository information (user/repo format)<br />
– Workflow filename<br />
– Branch reference (default: main)<br />
– GitHub personal access token for authentication</p>
<p>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.</p>
<p>This service is provided by GitHub, Inc.:<br />
– Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service<br />
– Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement</p>


Deploy Trigger for GitHub

Trigger GitHub Actions workflows from WordPress when content changes. Perfect for headless WordPress setups.

nicolasdra

<h3>DEPLOY WEBHOOK GITHUB ACTIONS PLUGIN</h3>
<p>A WordPress plugin to manually trigger a deploy workflow via the Github Actions REST API after updating content.</p>
<h3>FEATURE</h3>
<p>Trigger a deploy workflow via Github Actions after updating content. Users with manage_capabilities are only allowed to perform the action from the the WordPress admin menu.</p>
<h3>SETTINGS</h3>
<p>Fill out the form with the data required on the Settings Page. Find a reference below:</p>
<p>OWNER: The username or organization name that owns the repository.<br />
REPO: The name of the repository.<br />
WORKFLOW_ID: You can either write the full name of your .yml file, ie. “manual-trigger-workflow.yml” or the ID of the workflow that you want to trigger. You can find the ID of a workflow by going to the “Actions” tab of your repository on GitHub, clicking on the name of the workflow, and looking at the URL of the page. The ID is the number that appears after the last forward slash in the URL.<br />
PERSONAL_ACCESS_TOKEN: A personal access token (PAT) with the repo scope. You can create a PAT by going to “Settings” > “Developer settings” > “Personal access tokens” in your GitHub account.<br />
REF: The name of your repository’s main branch. Important: At the moment the plugin is able to create a webhook for a workflow_dispatch trigger without inputs. This feature is planned for later versions.</p>
<h3>TO DO</h3>
<p>Add feature: accept inputs.</p>
<h3>AUTHOR</h3>
<p>Created by Nicolás di Rago.<br />
https://www.nicolasdirago.com/</p>


Deploy Trigger for GitHub vs Deploy Webhook Github Actions