Skip to content

Add SVN Checker Admin Page - #1437

Open
ernilambar wants to merge 11 commits into
trunkfrom
1434-svn-checker
Open

Add SVN Checker Admin Page#1437
ernilambar wants to merge 11 commits into
trunkfrom
1434-svn-checker

Conversation

@ernilambar

@ernilambar ernilambar commented Aug 8, 2026

Copy link
Copy Markdown
Member

Fixes #1434

Summary

  • Create SVN Checker admin menu page
  • Implement AJAX handler for plugin slug checks
  • Add JavaScript for asynchronous report rendering
  • Add CSS for checker UI and status badges
  • Add PHP unit tests for the changes

Screenshot

Screenshot 2026-08-10 at 11 43 57 AM Open WordPress Playground Preview

@ernilambar
ernilambar force-pushed the 1434-svn-checker branch 2 times, most recently from c6e215e to b00452c Compare August 8, 2026 17:48
@ernilambar ernilambar changed the title feat: Add SVN checker Add SVN Checker Admin Page Aug 10, 2026
@ernilambar
ernilambar marked this pull request as ready for review August 10, 2026 07:31
@github-actions

github-actions Bot commented Aug 10, 2026

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: ernilambar <nilambar@git.wordpress.org>
Co-authored-by: frantorres <frantorres@git.wordpress.org>
Co-authored-by: davidperezgar <davidperez@git.wordpress.org>

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

@davidperezgar

Copy link
Copy Markdown
Member

Thanks @ernilambar for the tool. I see it's very useful.

Thanks to Codex’s review, I found a false positive for valid repositories using Stable tag: trunk.

The checker treats trunk as a release tag and checks tags/trunk/, then compares the literal value trunk with the plugin version. This produces failures for a valid WordPress.org configuration.

Could we skip the tag-directory section and stable-tag/version comparison when Stable tag is trunk, and add a regression test?

@ernilambar

Copy link
Copy Markdown
Member Author

@davidperezgar PR has been updated.

*/
public function add_page(): void {
$hook = add_management_page(
__( 'Plugin Check SVN Checker', 'plugin-check' ),

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I'd change to Plugin Check SVN. It won't break the line in the menu. When you go to the page, it can be named SVN Checker.

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.

Add SVN Checker tool

3 participants