Skip to content

chore: add wp-cli.yml and local dev environment docs#756

Merged
superdav42 merged 1 commit intomainfrom
chore/wp-cli-local-dev-docs
Apr 8, 2026
Merged

chore: add wp-cli.yml and local dev environment docs#756
superdav42 merged 1 commit intomainfrom
chore/wp-cli-local-dev-docs

Conversation

@superdav42
Copy link
Copy Markdown
Collaborator

@superdav42 superdav42 commented Apr 8, 2026

Point wp-cli at shared WordPress 7.0-RC2 multisite dev install at ../wordpress (wordpress.local:8080). Documents reset workflow and WP-CLI usage in AGENTS.md.

Summary by CodeRabbit

Release Notes

  • Documentation

    • Added comprehensive local development environment setup guide, including configuration details, reset procedures, and command-line tool examples.
  • Chores

    • Added configuration file for command-line tool integration with development environment.

Point wp-cli at shared WordPress 7.0-RC2 multisite dev install at
../wordpress (wordpress.local:8080). Documents reset workflow and
WP-CLI usage in AGENTS.md.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 8, 2026

📝 Walkthrough

Walkthrough

Added local development environment documentation to AGENTS.md describing the shared WordPress installation, credentials, and configuration. Created a new wp-cli.yml configuration file specifying the WordPress path and local URL for WP-CLI command execution.

Changes

Cohort / File(s) Summary
Local Development Documentation
AGENTS.md
Added "Local Development Environment" section documenting the shared WordPress dev install at ../wordpress, local URL (http://wordpress.local:8080), WordPress version (7.0-RC2), plugin symlink strategy, reset procedures, WP-CLI configuration, and example commands for plugin activation/deactivation and database operations.
WP-CLI Configuration
wp-cli.yml
Created new configuration file with path pointing to the shared WordPress installation (../wordpress) and local development URL (http://wordpress.local:8080).

Possibly Related PRs

Poem

🐰 A wordpress burrow in the local nest,
Config and docs make the dev life blessed,
With wp-cli commands and a shared reset,
The agents now know where to rest! 🌱

Estimated Code Review Effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes both main changes: adding wp-cli.yml configuration and documenting the local dev environment in AGENTS.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/wp-cli-local-dev-docs

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

🔨 Build Complete - Ready for Testing!

📦 Download Build Artifact (Recommended)

Download the zip build, upload to WordPress and test:

🌐 Test in WordPress Playground (Very Experimental)

Click the link below to instantly test this PR in your browser - no installation needed!
Playground support for multisite is very limitied, hopefully it will get better in the future.

🚀 Launch in Playground

Login credentials: admin / password

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
AGENTS.md (1)

173-177: Consider adding a note about the reset.sh dependency.

The command examples are functional, but the ./reset.sh script on line 176 is referenced without explanation. Consider briefly documenting what reset.sh does or noting that it must exist in the ../wordpress directory.

📝 Suggested documentation clarification
 ```bash
 wp plugin activate $(basename $PWD)   # activate this plugin
 wp plugin deactivate $(basename $PWD) # deactivate
-wp db reset --yes && cd ../wordpress && ./reset.sh  # full reset
+wp db reset --yes && cd ../wordpress && ./reset.sh  # full DB + WordPress reset (requires reset.sh in ../wordpress)
</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

Verify each finding against the current code and only fix it if needed.

In @AGENTS.md around lines 173 - 177, Add a brief note in AGENTS.md next to the
example command that ./reset.sh is a required script located in the
../wordpress directory and describe its purpose (e.g., resets WordPress
installation and assets) so users know the dependency and what the script does;
update the comment on the wp db reset --yes && cd ../wordpress && ./reset.sh
example to mention "requires reset.sh in ../wordpress" and a short parenthetical
like "(performs full WordPress reset)" to clarify intent.


</details>

</blockquote></details>

</blockquote></details>

<details>
<summary>🤖 Prompt for all review comments with AI agents</summary>

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @AGENTS.md:

  • Line 167: Update the WordPress version in the AGENTS.md line that currently
    reads "WordPress version: 7.0-RC2" to reference the latest stable release
    "WordPress version: 6.9.4" so the documentation points to a stable release
    instead of a pre-release.

Nitpick comments:
In @AGENTS.md:

  • Around line 173-177: Add a brief note in AGENTS.md next to the example command
    that ./reset.sh is a required script located in the ../wordpress directory and
    describe its purpose (e.g., resets WordPress installation and assets) so users
    know the dependency and what the script does; update the comment on the wp db reset --yes && cd ../wordpress && ./reset.sh example to mention "requires
    reset.sh in ../wordpress" and a short parenthetical like "(performs full
    WordPress reset)" to clarify intent.

</details>

<details>
<summary>🪄 Autofix (Beta)</summary>

Fix all unresolved CodeRabbit comments on this PR:

- [ ] <!-- {"checkboxId": "4b0d0e0a-96d7-4f10-b296-3a18ea78f0b9"} --> Push a commit to this branch (recommended)
- [ ] <!-- {"checkboxId": "ff5b1114-7d8c-49e6-8ac1-43f82af23a33"} --> Create a new PR with the fixes

</details>

---

<details>
<summary>ℹ️ Review info</summary>

<details>
<summary>⚙️ Run configuration</summary>

**Configuration used**: defaults

**Review profile**: CHILL

**Plan**: Pro

**Run ID**: `2cb98cf5-17aa-48b2-a427-ae3aca58e9f9`

</details>

<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 3698e2769d60c4aa898a6aafa499349a0db5af19 and 0610e08d59df2d5c0ea732581c69f179120657dd.

</details>

<details>
<summary>📒 Files selected for processing (2)</summary>

* `AGENTS.md`
* `wp-cli.yml`

</details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->


- **URL**: http://wordpress.local:8080
- **Admin**: http://wordpress.local:8080/wp-admin — `admin` / `admin`
- **WordPress version**: 7.0-RC2
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

What is the latest WordPress version as of April 2026?

💡 Result:

As of April 2026 (including April 8, 2026), the latest stable WordPress release is WordPress 6.9.4 (a security release), published March 11, 2026. [1] [2]

Note: WordPress 7.0 was still in release-candidate status in late March 2026, not yet the latest stable release. [3]

Sources:
[1] https://wordpress.org/download/
[2] https://wordpress.org/news/2026/03/wordpress-6-9-4-release/
[3] https://wordpress.org/news/


Consider using WordPress 6.9.4 (stable) instead of 7.0-RC2.

WordPress 7.0-RC2 is a pre-release version. As of April 2026, the latest stable release is WordPress 6.9.4 (released March 11, 2026). Documentation should reference stable versions when possible.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@AGENTS.md` at line 167, Update the WordPress version in the AGENTS.md line
that currently reads "**WordPress version**: 7.0-RC2" to reference the latest
stable release "**WordPress version**: 6.9.4" so the documentation points to a
stable release instead of a pre-release.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

Performance Test Results

Performance test results for ed2262a are in 🛎️!

Note: the numbers in parentheses show the difference to the previous (baseline) test run. Differences below 2% or 0.5 in absolute values are not shown.

URL: /

Run DB Queries Memory Before Template Template WP Total LCP TTFB LCP - TTFB
0 40 37.77 MB 871.00 ms (+41.00 ms / +5% ) 166.00 ms (+9.50 ms / +6% ) 1073.00 ms 2062.00 ms 1981.25 ms 92.05 ms
1 56 49.02 MB 967.50 ms 152.00 ms 1118.00 ms 2094.00 ms 2016.80 ms 84.40 ms

@superdav42 superdav42 merged commit 6b28c6f into main Apr 8, 2026
11 checks passed
@superdav42
Copy link
Copy Markdown
Collaborator Author

Point wp-cli at shared WordPress 7.0-RC2 multisite dev install at ../wordpress (wordpress.local:8080). Documents reset workflow and WP-CLI usage in AGENTS.md.


Merged via PR #756 to main.
Merged by deterministic merge pass (pulse-wrapper.sh).

aidevops.sh v3.6.166 spent 6m on this as a headless bash routine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant