Skip to content

ci: accept 503 in the deploy link check #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rivassec merged 1 commit into from
Oct 10, 2026
Merged

ci: accept 503 in the deploy link check #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion .github/workflows/deploy.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,14 +89,19 @@ jobs:
# URL exclusions live in .lycheeignore (single source of truth, shared
# with the weekly link-rot workflow; lychee reads it automatically).
# Path exclusions stay inline: .lycheeignore holds URL patterns only.
# 503 is accepted because github.com throttles Actions runners on
# /blob/ pages for hours at a time (2026-10-10: every deploy blocked
# while the same URLs returned 200 elsewhere). A 503 says nothing
# about whether a link is broken, so it must not block a deploy;
# 404s still fail, and the weekly link-rot job still reports 503s.
uses: lycheeverse/lychee-action@e7477775783ea5526144ba13e8db5eec57747ce8 # v2.9.0
with:
args: >-
--no-progress
--base https://rivassec.com
--remap "https://rivassec.com/ file://${{ github.workspace }}/output/"
--verbose
--accept 200..=299,429
--accept 200..=299,429,503
--max-retries 5
--retry-wait-time 2
--exclude-path output/feeds
Expand Down
Loading