Skip to content
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

Set Up Plugin-Check #274

Open
vikrampm1 opened this issue Jan 17, 2025 · 0 comments · May be fixed by #271
Open

Set Up Plugin-Check #274

vikrampm1 opened this issue Jan 17, 2025 · 0 comments · May be fixed by #271
Assignees
Labels
priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically.

Comments

@vikrampm1
Copy link
Contributor

The WooCommerce team recently added the Plugin-Check tool as a new test type to QIT. The Plugin Check is a WordPress.org tool which provides checks to help plugins meet the directory requirements and follow various best practices. Hence, the goal of this task to add Plugin-Check to this extension and ensure it is properly set up and checks are passed prior to releases.

Currently, only checks from the plugin_repo category will be run; these should flag obvious violations of the wordpress.org plugin review guidelines.

GitHub Action to add: https://github.com/WordPress/plugin-check-action

Documentation: https://qit.woo.com/docs/managed-tests/plugin-check/

@vikrampm1 vikrampm1 added the priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically. label Jan 17, 2025
@vikrampm1 vikrampm1 added this to the Future Release milestone Jan 17, 2025
@vikrampm1 vikrampm1 linked a pull request Jan 17, 2025 that will close this issue
4 tasks
@faisal-alvi faisal-alvi linked a pull request Jan 21, 2025 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The issue/PR is high priority—if affect lots of customers substantially, but not critically.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants