Skip to content

Ignore .wp-env.test.override.json#484

Merged
gziolo merged 1 commit intoWordPress:developfrom
t-hamano:ignore-test-override-file
Apr 29, 2026
Merged

Ignore .wp-env.test.override.json#484
gziolo merged 1 commit intoWordPress:developfrom
t-hamano:ignore-test-override-file

Conversation

@t-hamano
Copy link
Copy Markdown
Contributor

@t-hamano t-hamano commented Apr 29, 2026

Follow-up to #447

What?

Adds /.wp-env.test.override.json to .gitignore so a local test-only wp-env override file is never tracked.

Why?

Sometimes, we might want to change the settings of our test environment, not just our development environment, locally.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 4.7
Used for: Drafting the commit message and PR description; the change itself is a one-line .gitignore addition reviewed and verified by me.

Changelog Entry

Development Update - Ignore /.wp-env.test.override.json so local test-only wp-env overrides stay untracked.

Open WordPress Playground Preview

@t-hamano t-hamano marked this pull request as ready for review April 29, 2026 04:04
@github-actions
Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: t-hamano <wildworks@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 29, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.06%. Comparing base (a44e792) to head (a17722e).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #484   +/-   ##
==========================================
  Coverage      69.06%   69.06%           
  Complexity       957      957           
==========================================
  Files             60       60           
  Lines           4512     4512           
==========================================
  Hits            3116     3116           
  Misses          1396     1396           
Flag Coverage Δ
unit 69.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@gziolo gziolo added the [Tool] Issues related to development tooling, such as linting, testing, or CI label Apr 29, 2026
@gziolo gziolo merged commit 7edda9c into WordPress:develop Apr 29, 2026
20 of 33 checks passed
@jeffpaul jeffpaul added this to the 0.9.0 milestone May 4, 2026
@jeffpaul jeffpaul moved this from Done to Needs review in WordPress AI Planning & Roadmap May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Tool] Issues related to development tooling, such as linting, testing, or CI

Projects

Status: Needs review

Development

Successfully merging this pull request may close these issues.

3 participants