-
Notifications
You must be signed in to change notification settings - Fork 138
Merge feature/modules-to-plugins into feature/auto-sizes
#975
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
Co-authored-by: Pascal Birchler <[email protected]>
Introduce plugins folder for standalone plugins
Merge trunk into feature/modules-to-plugins
…ance into add/plugins-test-suite
Merge trunk into feature/modules-to-plugins
Add test suite for Plugins folder
|
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 Core SVNCore Committers: Use this line as a base for the props when committing in SVN: GitHub Merge commitsIf 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. |
joemcgill
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ I'm confused about why we are merging the feature/modules-to-plugins branch into the feature/auto-sizes branch, when #904 suggests the opposite.
I need approval to merge the changes already committed to the feature branch.
Checklist
[Focus]orInfrastructurelabel.[Type]label.no milestonelabel.