MR-15: Local dev env and CI/CD pipelines#19
Conversation
# Conflicts: # .gitignore # js/src/expiry-banner.js # package-lock.json # src/expiry_banner.php # views/expiry-banner.php
|
Warning Review limit reached
More reviews will be available in 23 minutes and 41 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository: TheCodeCompany/coderabbit/.coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (25)
📒 Files selected for processing (131)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
av3nger
changed the title
av3nger
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 7c8fce6. Configure here.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
1 participant
Summary
Modernises the plugin's tooling - repo layout, local dev environment, automated tests, linting, and the release pipeline. The plugin now lives at the repo root, local dev runs on
wp-env, and CI covers tests, PHP compatibility, and coding standards. Releases to WordPress.org are automated from GitHub Releases.What's included
@wordpress/env(.wp-env.json+env:*npm scripts);assets/→.wordpress-org/.bin/install-wp-tests.sh;phpunit.ymlCI matrix (PHP 7.4–8.4 × WP, multisite, nightly).phpcs.xml(WordPress standard, 2-space) +.editorconfig;composer lint/compatscripts;lint.ymlwith a blocking PHP 7.4+ compatibility gate and advisory coding-standards job (legacy backlog).phpcs-changedon staged PHP - checks only changed lines, so the legacy backlog never blocks a commit..distignore(ships only the plugin; keepsvendor/reporting.php);deploy.yml;build-zip.yml(manualworkflow_dispatchto build a test zip from any branch).Test plan
composer compat→ exits 0 (blocking gate, PHP 7.4+).composer lint→ runs; legacy findings are advisory only (does not block).--no-verifybypasses.src/,views/,js/build/,vendor/reporting.phpand excludesnode_modules/,tests/,js/src/, dev configs.SVN_USERNAME/SVN_PASSWORDsecrets; tag with the bare version (e.g.1.78.0) - a mismatched tag fails the version check. Optionallydry-run: trueonce before a real release.npm run env:startto init a local environment using DockerOn latest node versions, if the wp-env command fails with
ETIMEDOUTerror, run the following command beforenpm run env:start:export NODE_OPTIONS="--network-family-autoselection-attempt-timeout=5000 --dns-result-order=ipv4first"Note
Medium Risk
No plugin runtime logic changes in the diff, but automated WordPress.org SVN deploy and packaging rules directly affect what ships to production sites if misconfigured.
Overview
Flattens the plugin to the repository root and retires the Docker Compose stack (
docker-compose.yml,docker-provision.sh,envfile) in favor of@wordpress/envvia.wp-env.jsonandenv:*npm scripts. Contributor docs (README.md,AGENTS.md) and WordPress.org assets move to.wordpress-org/.Adds Composer dev tooling (
composer.json) with PHPUnit, PHPCS, and PHP 7.4+ compatibility checks, plusbin/install-wp-tests.shfor the CI test harness. GitHub Actions run a PHPUnit matrix (phpunit.yml), a blocking compat gate and advisory PHPCS (lint.yml), manual release zips (build-zip.yml), and WordPress.org deploy on GitHub release (deploy.yml) with tag vsreadme.txtStable tag validation and zip upload..distignoredefines what ships to SVN (dev files excluded;vendor/reporting.phpstill ships via gitignore strategy)..gitignorenow ignoresnode_modules, build output, and Composer vendor except committedvendor/reporting.php. Husky + lint-staged runphpcs-changedon staged PHP in pre-commit.Reviewed by Cursor Bugbot for commit 472f33f. Bugbot is set up for automated code reviews on this repo. Configure here.