Conversation
|
✅ The link checker did not find any broken links. See more at https://github.com/apify/apify-client-js/actions/runs/22486423697#summary-65137089864 |
|
edit: the GH action has been moved to a separate PR cc: reviewers, we might want to port this (the gh action) to the other documented projects as well. wdyt? The link checking step will always pass, even with 404s. The only change is this comment - see its edit history for more context. If there are no broken links to begin with, this comment won't be generated to keep the spam levels low. |
|
This has been discussed w/ @TC-MO today, as the Docs team wants to unify the docs checks in |
This comment was marked as resolved.
This comment was marked as resolved.
|
Shouldn't we also add redirects for this? |
|
fwd @TC-MO do you recall moving any of these links recently? I wouldn't bother w/ the API docs links (it's just two endpoints, likely broken by the switch to a different API docs rendering plugin), but the Academy pages might have been linked from other places too |
|
IIRC last time we touched any API reference links was during the reorganization ~last year PR for reference : click |
|
To answer @B4nan 's question, I couldn't find the old links in any of our other docs, nor in The Wayback Machine (the correct / new URL for the Academy page dates back to 2023). This leads me to the conclusion that these were some one-off mistakes, and we probably don't have to bother with redirects here. |
related slack thread