Enhancement: add Plugin Check to existing test/lint tasks

Open
#2,552 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
node.js, php
Domain
ci-cd, testing-qa, tooling

Research direction

Start by inspecting the npm scripts behind npm run lint-php and npm run test-php{-plugin}, then review how Plugin Check currently runs in CI. Done means the relevant local lint or test tasks invoke Plugin Check and report its failures before CI, with the existing PHP tasks still working.

Written by the indexing model from the issue text.

Description

Feature Description

I am working on a PR and CI threw an error from Plugin Check. This is fine, but it would have been better if I found that out in my local IDE rather than waiting for CI to reveal it.

Is there a way to run plugin check when we do something like npm run lint-php or npm run test-php{-plugin}?

AI has suggestions, but I suspect theyre very sub-optimal. Someone on the team surely has a good idea.

Dominant language
PHP
Stars
461
Forks
165
Avg merge
11h 12m
Merged PRs (30d)
28

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from WordPress/performance

All issues in WordPress/performance

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.