Skip to content

Rename new submenu item for redirects#22611

Merged
thijsoo merged 1 commit intotrunkfrom
fix/naming-redirects-tools-page
Oct 2, 2025
Merged

Rename new submenu item for redirects#22611
thijsoo merged 1 commit intotrunkfrom
fix/naming-redirects-tools-page

Conversation

@leonidasmi
Copy link
Copy Markdown
Contributor

Context

Summary

This PR can be summarized in the following changelog entry:

  • Rename new submenu item for redirects, to Yoast redirects.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Confirm that the new submenu item under Tools, is named Yoast redirects.

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@leonidasmi leonidasmi added required-for-rc An issue that needs to be addressed before the next RC is created changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog labels Oct 1, 2025
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build 84d8d6e44afdf212173f08c4bf9422a27fc71bc4

Details

  • 0 of 6 (0.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.5%) to 52.749%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/integrations/admin/redirections-tools-page.php 0 6 0.0%
Totals Coverage Status
Change from base Build 52ee80b3ac3925ed07c59dca93065386cbdfc3d2: -0.5%
Covered Lines: 31264
Relevant Lines: 59411

💛 - Coveralls

Copy link
Copy Markdown
Contributor

@thijsoo thijsoo left a comment

Choose a reason for hiding this comment

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

CR + ACC 👍

@thijsoo thijsoo added this to the 26.2 milestone Oct 2, 2025
@thijsoo thijsoo merged commit 672a2ac into trunk Oct 2, 2025
27 of 29 checks passed
@thijsoo thijsoo deleted the fix/naming-redirects-tools-page branch October 2, 2025 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog required-for-rc An issue that needs to be addressed before the next RC is created

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants