Fix Abilities Explorer page heading#585
Conversation
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #585 +/- ##
=============================================
+ Coverage 71.41% 72.40% +0.99%
- Complexity 1158 1162 +4
=============================================
Files 67 68 +1
Lines 5586 5596 +10
=============================================
+ Hits 3989 4052 +63
+ Misses 1597 1544 -53
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
What?
Fixes the Abilities Explorer admin page heading so it matches the feature name used everywhere else in the UI.
The page title and Tools menu already use “Abilities Explorer”, but the page heading showed “Ability Explorer”.
Why?
The mismatch is visible in the WordPress admin and makes the experiment name inconsistent across the same screen.
How?
<h1>from “Ability Explorer” to “Abilities Explorer”.Testing Instructions
Automated checks run locally:
Focused Abilities Explorer E2E passed:
Full E2E was also run:
The Abilities Explorer tests passed in the full run. The full suite had unrelated failures outside this patch area.
Screenshots/Screencast
Before
The page heading showed “Ability Explorer”, while the menu and browser title showed “Abilities Explorer”.
After
The page heading now matches the menu and browser title.
Use of AI Tools
AI assistance: Yes
Tool(s): ChatGPT / Codex
Used for: Repository review, reproduction planning, implementation guidance, test updates, and local verification. I reviewed the changes, tested the behavior locally, and take responsibility for the final submission.