Skip to content

[N/A] WP Engine branch deploys - #296

Draft
bd-viget wants to merge 2 commits into
mainfrom
bd/na-wpe-branch-deploys
Draft

bd-viget wants to merge 2 commits into
mainfrom
bd/na-wpe-branch-deploys

Conversation

@bd-viget

@bd-viget bd-viget commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Ports the WP Engine branch deploys from WebsterRenold (websterrenold#28) so new projects ship with them.

  • Pushing to dev, staging or production builds the site and rsyncs it to the WP Engine install for that branch in wpengine.conf.
  • The build steps live in a build-site composite action. The PR check and the deploy both use it.
  • The starter's own demo deploy is now deploy-starter.yaml, and the Composer script tests are their own starter-tests.yaml workflow. create-project removes both, plus tests/ and phpunit.xml.dist. The tests job was failing on every PR in generated projects since they have no root composer.json.
  • WPE_INSTALL_prod is now WPE_INSTALL_production so the branch, GitHub environment and config key all match.
  • Deployment docs are in docs/deployment.md, linked from README.dist.md.
  • This replaces the Git Push deploy (build_deploy.yaml) we've been copying between WPE projects. It rsyncs over the SSH Gateway with WP Engine's own deploy action, lets a running deploy finish, and clears cache over SSH with the same deploy key.
  • build-site reads the PHP version from .ddev/config.yaml's php_version, same as Node from .nvmrc. WebsterRenold pins 8.4 in the action.
  • Added a job-level branch guard to deploy.yaml so a manual run from any other branch doesn't create a stray GitHub environment.

Issues

  • N/A

Testing Instructions

  1. Confirm the Build Theme and Starter Tests checks pass.
  2. Run composer create-project from this branch and confirm deploy-starter.yaml, starter-tests.yaml, release.yaml, tests/ and phpunit.xml.dist are gone, and deploy.yaml, build.yaml, .github/actions/build-site/ and docs/deployment.md reference the project's theme slug.

Screenshots

N/A

🤖 Generated with Claude Code

https://claude.ai/code/session_01FDZroxqnut3VBpPCvW7j9Q

bd-viget and others added 2 commits October 2, 2026 13:14
Pushes to dev, staging or production build the site and rsync it to the
matching WP Engine install. Build steps move to a build-site composite
action shared by the PR check and the deploy.

The starter's demo-site deploy moves to deploy-starter.yaml and its
Composer script tests to starter-tests.yaml. create-project removes both,
along with tests/ and phpunit.xml.dist, so generated projects keep only
the WP Engine deploy and a build check that passes.

Deployment docs live in docs/deployment.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FDZroxqnut3VBpPCvW7j9Q
build-site takes PHP from .ddev/config.yaml's php_version, the way Node
comes from .nvmrc, so CI matches each project's DDEV and host without a
second pin. db-sync's SSH checklist now refers to the deploy user's key.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FDZroxqnut3VBpPCvW7j9Q
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant