As a developer i want to create a new environment when a new PR is opened so i can test that PR’s Code in isolation without having to merge the code to dev

[chrillep]

I’d like to create new envs via trellis when a PR is created.

Acceptance Criterias

• should use copy of staging db
• should use copy of envs from staging
• environment should use PR ID
• should use a domain with PR ID
• should be compatible with github actions.
• should be created when a new PR is opened
• should get changes from newer commits in PR
• should be deleted when PR is closed
• should be deleted when PR branch is deleted

[MWDelaney]

It doesn’t cover all of your use cases, but take a look at this, particularly the examples, which includes a dry-run action.

Trellis Deployment with GitHub Actions

Introducing Trellis GitHub Deployment. Trellis GitHub Deployment Automatically deploy your Trellis-based WordPress site to staging and production environments on merge to staging and main branches respectively, and keep plugins, themes, and WordPress core up to date with Dependabot. Features Automatic (or manual) deployment to staging and production environments using GitHub Actions when pull requests are merged to your staging and main branches respectively. …

[MWDelaney]

Trellis’s own integration test makes the brilliant move of provisioning the VM it’s running on (cheers, @swalkinshaw), which might help too:

roots/trellis/blob/c9f4dd918cb0a708b298c506785b09c7e0e80e3a/.github/workflows/integration.yml