-
-
Notifications
You must be signed in to change notification settings - Fork 51
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem setting max-redirect arg on action #164
Labels
enhancement
New feature or request
Comments
mre
added a commit
to lycheeverse/lychee
that referenced
this issue
Mar 10, 2023
Having more than the max number of redirects caused lychee to abort the requests, but did not lead to an error. lycheeverse/lychee-action#164
mre
added a commit
to lycheeverse/lychee
that referenced
this issue
Mar 10, 2023
Having more than the max number of redirects caused lychee to abort the requests, but did not lead to an error. lycheeverse/lychee-action#164
mre
added a commit
to lycheeverse/lychee
that referenced
this issue
Mar 10, 2023
Having more than the max number of redirects caused lychee to abort the requests, but did not lead to an error. lycheeverse/lychee-action#164
mre
added a commit
to lycheeverse/lychee
that referenced
this issue
Mar 10, 2023
Having more than the max number of redirects caused lychee to abort the requests, but did not lead to an error. Related: lycheeverse/lychee-action#164
This was resolved in lycheeverse/lychee#987. In |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe this is an upstream issue; let me know if it is.
Summary
Background: I'm in the process of updating GitHub's Octokit.net codebase to use newer doc links. Currently, many of their links are 301 permanently redirected.
Goal: I'd like to use the lychee-action to fail on links that are redirected.
What I tried: specifying
args: --max-redirects 0
in the GitHub Action YAML for the action. (tried with quotes as well)What I expected: Many failed links due to lots of 301 redirects.
What actually happened: Looks like the action itself failed to run, noting that I had not specified
<inputs>
.Links
The text was updated successfully, but these errors were encountered: