Facundo

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.
<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>
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’s API: 
– Repository information (user/repo format) 
– Workflow filename 
– Branch reference (default: main) 
– 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.: 
– Terms of Service: https://docs.github.com/en/site-policy/github-terms/github-terms-of-service 
– Privacy Policy: https://docs.github.com/en/site-policy/privacy-policies/github-privacy-statement

Deploy Trigger for GitHub

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

jwong.dayspring

Copy Post removes the tedium of having to copy content, comments, and tags manually from one instance to another. It also preserves the original post author and date.
Copy Post was originally written when we were preparing to launch a public blog and wanted to pre-populate it with content from our in-office blog that we had been using for the past two years. If our marketing team thinks that something originally posted to our in-office blog would be helpful or meaningful to others outside of our company, they can easily copy it to the public blog. 
Copy Post could also be used in a situation where multiple WordPress instances are used in a development/staging/production setup.
First, a few assumptions and caveats.
<ul>
<li>You must have access to the MySQL database of the destination blog.</li>
<li>The author of the post you are copying must have an account on the destination blog with the same login name, though the IDs don’t have to be the same.</li>
<li>Categories assignments are not copied over, mainly because in our case the categories on the two blogs are different and were going to be edited anyway.</li>
<li>Comments attributed to registered users retain this attribution only if the commenter has an account on the destination blog (just like the author). If the commenter doesn’t have an account, the comment is still copied, but it’s treated as if it were made by an unregistered visitor.</li>
</ul>
Use the copy post feature to send a post to a destination blog. You’ll need the post ID, which is available by looking at the edit link for the post. The plugin will copy the post content, tags, and comments. The original author and post date will be retained. All category information will not be copied over. The resulting post will be set as a “private” post to allow you to set the categories and make edits before it goes live. Also, you’ll need to be an admin on the source blog to use the plugin.
The settings for the destination blog are configured directly in the WordPress Admin interface, making it possible for us to distribute the plugin to anyone who would need it.

Copy Post

Copy Post allows you to copy posts from one instance of WordPress to another.

Deploy Trigger for GitHub vs Copy Post