treat 403 as warning instead of error in link checker - #306
Merged
Conversation
✅ Deploy Preview for ucospo-net ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
LauraLangdon
force-pushed
the
fix-linkinator-slack-retry
branch
from
April 29, 2026 21:22
375d901 to
bbc5025
Compare
LauraLangdon
marked this pull request as ready for review
April 29, 2026 21:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CI failure on #305 is from linkinator getting a 403 on our Slack invite link. The link itself is fine and doesn't expire until 2030. Instead, Slack appears to have recently tightened bot protection for invite URLs coming from CI runners. The same link returns 302 (normal redirect) from a regular machine but 403 from CI runners. I checked the logs—the exact same link returned 200 on every CI run through April 22, then started returning 403 on April 28. Same linkinator version, same config, same link. Nothing changed on our side.
Rather than skipping Slack links entirely (we want to know if an invite link actually expires), this treats all 403s as warnings instead of errors. A 403 will still show up in the build logs, but it won't block PRs. If a link genuinely dies, it'll return 404 or redirect, which will still fail the build.