WIP: Use "--no-progress" to suppress redirects messages#4349
Draft
WIP: Use "--no-progress" to suppress redirects messages#4349
Conversation
seisman
changed the title
Member
Author
|
Update: It seems the issue has been fixed by upstream (lycheeverse/lychee#1934, lycheeverse/lychee#2043), and a new version v0.23.0 was released. But the action still defaults to v0.21.0, so we need to wait for more days or explicitly pin the lychee version to v0.23.0. |
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.
Address #4348 (comment).
Related to upstream issue lycheeverse/lychee#1934.
Adding
--no-progressalone can't exclude the "redirects" records. Have to add--format compacttoo, but the issue report (#4350) is not ideal.