Skip to content
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.

Create staging_workshop.yml #94

Merged
merged 3 commits into from
Oct 13, 2021
Merged

Create staging_workshop.yml #94

merged 3 commits into from
Oct 13, 2021

Conversation

pbking
Copy link
Contributor

@pbking pbking commented Oct 12, 2021

Adding a deploy action on changes to /trunk for https://twentytwentytwo-trunk.mystagingwebsite.com/

Description

This deploys the content of the repo to the /themes folder in the noted site. The expectation is that this would be the "workshop" where there will be many examples of different types of content and edge conditions.

The "starting content" is the theme-test-data.

A separate site (likely 2022.wordpress.net) should also be setup to be a more "public face" of the theme with content better designed to demonstrate the strengths of the theme and properly achieve the design targets.

STAGING_USER and STAGING_PASSWORD values will need to be stored as secrets in order for this action to work.

Addresses #21 (though I still think 2022.wordpress.net would benefit from an automated deployment alongside this)

Copy link
Collaborator

@jffng jffng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added the respective secrets to the repository, so we should be all set.

Left one small comment about the workflow name, thank you for setting this up @pbking !

Co-authored-by: Jeff Ong <jonger4@gmail.com>
@jffng jffng merged commit 98f10dd into WordPress:trunk Oct 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants