Brandon Payton
Brandon Payton
Instead of saying "separate DSLs", we could instead say things like: - Language selection belongs outside the "steps" list in the Blueprints schema - Directory mounts belong outside the "steps"...
Related to the platform vs actions idea, one question is: Does the order in which the step is included matter? Does it need to come before or after other steps?
> > Language selection belongs outside the "steps" list in the Blueprints schema Directory mounts belong outside the "steps" list in the Blueprints schema > > I agree, but steps...
> [Blueprint example to demonstrate calling the missing intl functions](https://playground.wordpress.net/#%7B%22preferredVersions%22:%7B%22php%22:%228.0%22,%22wp%22:%22latest%22%7D,%22phpExtensionBundles%22:%5B%22kitchen-sink%22%5D,%22features%22:%7B%7D,%22landingPage%22:%22/%22,%22steps%22:%5B%7B%22step%22:%22writeFile%22,%22path%22:%22/wordpress/wp-content/mu-plugins/error.php%22,%22data%22:%22%3C?php%20$coll%20%20=%20collator_create(%22en_US%22);%20$result%20=%20collator_compare($coll,%20%22string#1%22,%20%22string#2%22);%20error_log(print_r($result),%20true);%22%7D%5D%7D) GitHub keeps URI encoding additional characters in the example link, and Playground is not properly consuming it. Here's the link...
There is also documentation that refers to plugin-proxy.php, and we should update that as part of this issue.
`plugin-proxy.php` has the ability to grab GitHub artifacts based on GitHub-specific IDs. If we are going to replace `plugin-proxy.php` entirely, it will require folks integrating with Playground to provide the...
@adamziel I think this may have been accidentally closed when #1960 was merged because it was "Related to" this one. There are a good number of tasks left unfinished, and...
It looks like we can approach this differently. Instead of having our automation work based on when a "Needs Author's Reply" label, we can use the [`moveProjectCard` mutation](https://docs.github.com/en/graphql/reference/mutations#moveprojectcard) and the...
> And then there's nothing else that our board automation handles so we could just get rid of it and never fix a bug again. I'll go ahead and disable...
Getting this error when running `npm run dev`. Will need to look into it. ``` % npm run dev > [email protected] dev > nx dev playground-website > nx run playground-website:dev...