Reusable WordPress Workflows to increase our productivity instead of deploying in the "cowboy" style through FTP.
- Deploy Plugin in a LAMP server
- Deploy Theme in a LAMP server
- Deploy Plugin in a EC2 instance
- Deploy Theme in a EC2 instance
[To do]
Copy and paste the .yml file more suitable for your needs in the .github/workflows folder of your repository. If you still don't have a .github/workflows folder, create one.
Change the paths and save the secrets on the appropriate environment.
The most common trigger for the workflows on this repository is run after a push to the master branch:
on:
push:
branches: [master]
But as you can see, for the create release workflow, it is triggered when a tag is added to the branch.
on:
push:
tags:
- v*
I would recommend using on push tag trigger for your deployments workflows too, so the deployed version of your project will always reflect the latest release of your project. For more details about Workflow triggers, please refer to GitHub documentation.
You can configure custom environments according to your project needs:
jobs:
deploy:
name: Deploy WordPress Theme
runs-on: ubuntu-20.04
environment: production
For more details about setting GitHub environments, please refer to GitHub documentation
Contribute to adding new workflows samples for other needs or other needs through pull requests, inform about issues or even add some improvements ideas.
This repository is licensed under the MIT license.