-
Notifications
You must be signed in to change notification settings - Fork 33
Feat: wp playground integration #85
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
Conversation
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #85 +/- ##
=============================================
- Coverage 28.79% 27.33% -1.46%
+ Complexity 153 152 -1
=============================================
Files 14 14
Lines 903 900 -3
=============================================
- Hits 260 246 -14
- Misses 643 654 +11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Co-authored-by: Darin Kotter <[email protected]>
|
@dkotter without being able to validate the WPORG link works, feels like this is good enough to merge and come back to if there's an issue later? |
Still a few unresolved comments (#85 (comment) and #85 (comment)) but once those are fixed, yes, I see no issue with merging this in |
Removed the description of experimental AI features.
What?
Closes #79
Why?
To Enable plugin testing with WordPress Playground.
How?