- Notifications
You must be signed in to change notification settings - Fork62.5k
Optimize and clean up YAML frontmatter to fix redirects and link check errors#39321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
github-actionsbot commentedJul 15, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key:fpt: Free, Pro, Team;ghec: GitHub Enterprise Cloud;ghes: GitHub Enterprise Server 🤖 This comment isautomatically generated. |
@NirajDN Looks good! I'll get it merged once checks are passing. |
e84e477
Uh oh!
There was an error while loading.Please reload this page.
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out ourhelp wanted issues ⚡ |
@Sharra-writes Awesome, thank you! 🎉 Appreciate the quick review and merge. |
Why:
This PR addresses the failing CI checks related to redirects and link validation by cleaning up duplicate and outdated entries in the YAML frontmatter of the documentation file.
The previous frontmatter contained multiple duplicate redirects which caused link checker and redirect tests to fail.
What's being changed (if available, include any code snippets, screenshots, or gifs):
These changes improve the accuracy of redirect paths and fix link validation errors during automated tests.
Check off the following: