-
Notifications
You must be signed in to change notification settings - Fork 293
Replace nightly option with trunk. #1763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I fully agree, excellent idea @peterwilsoncc |
I tried to figure out how to do this without success sorry. Basically I couldn't figure out which file I should edit to update the version dropdown. I could get it working by adding an option to the dropdown manually in this code block but that does not seem to be the correct approach. Lines 346 to 360 in 0fd051a
Nor was I clear on whether I needed to add a remote asset paths config. |
Here is a related Slack thread where the Test team wanted to use Playground for beta previews. They ended up using this blueprint:
|
@peterwilsoncc sorry for waiting so long on a reply, here are a few useful links in the Playground code in case you would like to work on it.
|
The customize playground popover includes an option to run the nightly version of WordPress.
The action https://github.com/WordPress/wordpress-playground/actions/workflows/refresh-wordpress-nightly.yml pulls down the nightly each day and commits it to the repo and deploys (the action is currently failing but that's the idea at least). An example commit can be seen at 6be65fb
As the zip file is replaced each time, it has the effect of making the repo rather large.
Since #1705 and #1721 it's possible to run playground from trunk with a download from the WordPress/WordPress repository.
I propose the action for updating the nighly be removed and the dropdown be replaced with run trunk.
The text was updated successfully, but these errors were encountered: