some new commits cause redirect errors. Fixed this batch but should look into it more closely#1213
Conversation
…ook into it more closely
|
Test deployment successful!! (2026-03-27T01:32:50Z) |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
Ye've seen fit to trim the redirect map, shortening one path while tossing the Machine Learning FAQ entry into the briny deep. While the shorter name might please the eyes, deleting a redirect instead of updating it is a fine way to run our users aground on a 404 reef. If ye've renamed the file to fit the 24-character rule, have the decency to update the map so the poor souls can actually find their treasure.
| General/FAQs/What_is_a_core_file.md : Getting_Started/FAQs/What_is_a_core_file.md | ||
| General/FAQs/What_Is_A_Trusted_Device.md : Getting_Started/FAQs/What_Is_A_Trusted_Device.md | ||
| General/FAQs/What_is_Multiple_Factor_Authentication_MFA.md : Getting_Started/FAQs/What_is_Multiple_Factor_Authentication_MFA.md | ||
| General/FAQs/What_software_environments_are_optimised_for_Machine_Learning_and_data_science.md : Getting_Started/FAQs/What_software_environments_are_optimised_for_Machine_Learning_and_data_science.md |
There was a problem hiding this comment.
Ahoy! It seems this old map entry has been cast into the sea. While the original filename was as long as a kraken's tentacle, simply scuttling the redirect might lead poor sailors to a dreaded 404 page if the destination was merely renamed.
If the page still exists under a shorter, more shipshape name, ye should be updating this redirect, not deleting it. A proper captain ensures all paths lead to treasure, not to ruin.
References
- The style guide advises keeping filenames short to prevent wrapping in the navigation bar (around 24 characters). The filename in this removed redirect is excessively long, suggesting it may have been renamed. (link)
1 participant
No description provided.