zieladam
@zieladam on WordPress.org and Slack
- Member Since: February 16th, 2018
- Location: Wroclaw, Poland
- Website: adamziel.com
- GitHub: adamziel
- Employer: Automattic
Interests
Contributions Sponsored
Contribution History
zieladam’s badges:- Core Contributor
- Core Team
- Documentation Contributor
- Training Contributor
-
Pull request #71 merged into WordPress/playground-tools:
Fix fatal startup crash on windows caused by an invalid mount() path -
Created issue #529 in the WordPress/wordpress-playground repository:
Blueprints: Mount local directories -
Created issue #527 in the WordPress/wordpress-playground repository:
PHP: Provide a nice error message in NodePHP.mount() when the VFS path... -
Submitted pull request #71 to WordPress/playground-tools:
Fix fatal startup crash on windows caused by an invalid mount() path -
Pushed 1 commit to WordPress/wordpress-playground:
v0.1.60 -
Merged pull request #524 into WordPress/wordpress-playground:
Pretend to activate plugin inside wp-admin -
Closed issue #131 on the WordPress/wordpress-playground repository:
Playground Roadmap -
Created issue #526 in the WordPress/wordpress-playground repository:
A recurrent slack meeting to triage issues, empower contributors, and discuss ideas -
Created issue #525 in the WordPress/wordpress-playground repository:
Roadmap -
Pushed 2 commits to WordPress/wordpress-playground:
CI: Add name to deploy_docs workflow -
Closed issue #172 on the WordPress/wordpress-playground repository:
GH action to release npm packages -
Pushed 1 commit to WordPress/wordpress-playground:
v0.1.59 -
Pushed 1 commit to WordPress/wordpress-playground:
CI: Add a missing npm install to "Publish NPM Packages"... -
Merged pull request #522 into WordPress/wordpress-playground:
Add automation for deploying npm packages -
Pushed 1 commit to WordPress/wordpress-playground:
v0.1.58 -
Submitted pull request #522 to WordPress/wordpress-playground:
Add automation for deploying npm packages -
Closed issue #171 on the WordPress/wordpress-playground repository:
GH action to deploy playground.wordpress.net -
Pushed 1 commit to WordPress/wordpress-playground:
Restrict the website deployment workflow to trunk -
Pushed 1 commit to WordPress/wordpress-playground:
Rename the website deploy workflow -
Merged pull request #521 into WordPress/wordpress-playground:
Automated deployments to playground.wordpress.net -
Submitted pull request #521 to WordPress/wordpress-playground:
Automated deployments to playground.wordpress.net -
Pushed 1 commit to WordPress/wordpress-playground:
Docs deploy: Use refs/head/trunk instead of refs/tags/trunk -
Closed issue #515 on the WordPress/wordpress-playground repository:
Auto deploy documentation site with GH actions -
Merged pull request #516 into WordPress/wordpress-playground:
GitHub Workflow: Deploy docs site on push to trunk -
Created issue #517 in the WordPress/wordpress-playground repository:
Blueprints: validate JSON -
Submitted pull request #516 to WordPress/wordpress-playground:
GitHub Workflow: Deploy docs site on push to trunk -
Created issue #515 in the WordPress/wordpress-playground repository:
Auto deploy documentation site with GH actions -
Created issue #514 in the WordPress/wordpress-playground repository:
PHP: Simplify the PHP interface structure -
Created issue #513 in the WordPress/wordpress-playground repository:
Doc: Link from Blueprints page to JS API page -
Created issue #512 in the WordPress/wordpress-playground repository:
Doc: Document all Blueprint steps -
Created issue #510 in the WordPress/wordpress-playground repository:
UX: Add an infobox to explain why Playground doesn't work when third-party... -
Closed issue #128 on the WordPress/wordpress-playground repository:
Feature Gallery -
Closed issue #473 on the WordPress/wordpress-playground repository:
Move Playground-based applications to dedicated repositories -
Closed issue #217 on the WordPress/wordpress-playground repository:
Tracking: Redesign Documentation -
Created issue #509 in the WordPress/wordpress-playground repository:
Doc: Include a brief overview of what WordPress Playground is and its... -
Created issue #508 in the WordPress/wordpress-playground repository:
Doc: How to debug a PHP.wasm issue? -
Created issue #507 in the WordPress/wordpress-playground repository:
Doc: Document the @wp-playground/nx-extensions:built-script executor -
Created issue #506 in the WordPress/wordpress-playground repository:
Doc: Document the test:esmcjs executor -
Created issue #505 in the WordPress/wordpress-playground repository:
Doc: Explain what are isomorphic packages -
Created issue #504 in the WordPress/wordpress-playground repository:
Doc: Discuss GPL Licensing in the contributing document -
Closed issue #423 on the WordPress/wordpress-playground repository:
Display a nice error on plugins.php -
Closed issue #450 on the WordPress/wordpress-playground repository:
PHP: Turn ExitStatus into a subclass of Error -
Closed issue #154 on the WordPress/wordpress-playground repository:
404 errors for missing assets/scripts when running `yarn run dev` -
Created issue #503 in the WordPress/wordpress-playground repository:
PHP: mount() should not create a directory when mounting a file -
Closed issue #202 on the WordPress/wordpress-playground repository:
mount() should call mkdirTree() internally -
Closed issue #59 on the WordPress/wordpress-playground repository:
Logging levels -
Created issue #63 in the WordPress/playground-tools repository:
Link to Playground docs in the Interactive Code Block -
Created issue #62 in the WordPress/playground-tools repository:
Submit the Interactive Code Block to the WordPress Plugin directory -
Created issue #61 in the WordPress/playground-tools repository:
Document Interactive Code Block -
Closed issue #17 on the WordPress/wordpress-playground repository:
A minimal runeditable code embed