Ignore the askubuntu link that now 403s the link checker - #106
Merged
Conversation
Stack Exchange started serving 403 to non-browser user agents, so htmlproofer fails on the askubuntu reference in the GRUB repair post. CI was green as recently as 2026-08-01, and nothing in the post changed — this is their bot wall, not a broken link. The target is alive: the URL redirects to askubuntu.com/questions/162564/how-can-i-tell-if-my-system-was-booted-as-efi-uefi-or-bios/162896 and the answer still renders in a browser. That matches the `ci-block` case the ignore list already documents, so add it there rather than touching the post. This blocks every open pull request against master, not just one, which is why it lands on its own. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Problem
CI is failing on every branch, including ones that touch nothing related:
Stack Exchange started serving 403 to non-browser user agents. CI was green as recently as 2026-08-01 and the post has not changed since — this is their bot wall, not link rot.
The link is alive
The answer still renders normally in a browser. This is exactly the
ci-blockcasescripts/testalready documents:So it goes in the ignore list next to the other four, rather than editing the post or weakening the check.
Why this is its own PR
It blocks every open pull request against master, not just one. Landing it separately means the others only need a rebase instead of each carrying a copy of the same unrelated fix.
Verification
./scripts/test:🤖 Generated with Claude Code