Setup build tooling and GitHub workflows #36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add GitHub Actions workflows for linting, testing, build/release, and PR previews - Configure WordPress Playground for local development and e2e testing - Add Playwright configuration and test infrastructure - Update package.json with playground and e2e test scripts - Change plugin version to __VERSION__ placeholder for automated release management - Remove build directory from version control (now generated during build process) - Add .gitignore entry for build directory The new workflow setup follows the established pattern from hm-url-tabs plugin: - Automated builds on main branch push - PR preview environments via WordPress Playground - E2e testing across multiple PHP and WordPress versions - Automatic cleanup of PR preview branches
- Add CLAUDE.md with plugin architecture and development documentation - Update blueprint.json to include advanced-query-loop plugin installation - Advanced Query Loop plugin is required for post type filtering functionality
- Keep __VERSION__ placeholder for automated version management - Keep build directory removed from version control - Maintain all workflow and configuration changes from setup branch
- Simplify workflow to use plugin-path and blueprint parameters - Remove invalid playground-url-path-params and playground-props inputs - Use current directory as plugin path after building - Reference blueprint.json for WordPress Playground configuration - Remove pr-cleanup workflow as we no longer create temporary branches
- Fix no-shadow errors by renaming callback parameters - Fix jsx-a11y/label-has-associated-control by adding htmlFor and id - Fix curly error by using braces for if statement - Fix react-hooks/exhaustive-deps by wrapping setAttributes in useCallback
- Break long onChange handlers onto multiple lines per WordPress coding standards
- Disable scss/at-rule-no-unknown for @view-transition at-rule - Disable property-no-unknown for navigation property - Both are valid CSS View Transitions API features
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new workflow setup follows the established pattern from hm-url-tabs plugin: