DanielLeens opened a new pull request, #12639: URL: https://github.com/apache/seatunnel/pull/12639
### Purpose of this pull request The `Dead links` job fails on every full scan and on every PR that touches `README.md`, for a reason unrelated to the change under test: the README's "Ask DeepWiki" badge links to `deepwiki.com`, and that host answers the link checker with HTTP 429 on every attempt. ``` [✖] https://deepwiki.com/apache/seatunnel → Status: 429 [✖] https://deepwiki.com/badge.svg → Status: 429 ERROR: 2 dead links found! ``` `.dlc.json` already sets `retryOn429` with `retryCount: 10`, and the job retries the whole file once more after 30 seconds; both passes end the same way, so this is the host refusing automated requests, not a transient limit. Occurrences in the last few days, all with exactly these two links as the only failing ones in `README.md`: - `dev` push build 36985353318 (2026-10-02) and both nightly `Schedule Backend` runs 37140101463 (10-03) and 37220159986 (10-04) - fork PR runs for #12512 (09-30), #12218 (10-04), #11746 and #11677 (10-05) ### Change Add `^https://deepwiki.com` to `ignorePatterns` in `.dlc.json`, next to the other badge and third-party hosts that reject automated requests (`img.shields.io`, `opencollective.com`, `mvnrepository.com`). The badge and its link stay in the README; only the checker stops probing that host. The job is `continue-on-error`, so this does not unblock merges by itself, but it removes a permanently red job from `dev` and from unrelated PRs, which makes real dead links visible again. ### Does this PR introduce _any_ user-facing change? No. CI configuration only. ### How was this patch tested? `.dlc.json` parses as valid JSON. The pattern uses the same anchored-prefix form as the existing entries. Verification is this PR's own `Dead links` job (a PR that changes no markdown checks no files) and the next `dev` full scan after merge. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
