New broken link checker ... broken

[tuminoid]

https://github.com/metal3-io/metal3-docs/actions/runs/15020538544/job/42208433545

Run lycheeverse/lychee-action@f796c8b7d468feb9b8c0a46da3fac0af6874d374
Run echo "$HOME/.local/bin" >> "$GITHUB_PATH"
Run # Remove any existing lychee binaries or archives to prevent conflicts
Run # Determine filename and download URL based on version
Downloading from: https://github.com/lycheeverse/lychee/releases/download/lychee-v0.18.0/lychee-x86_64-unknown-linux-gnu.tar.gz
Extracting lychee-x86_64-unknown-linux-gnu.tar.gz
lychee
Run install -t "$HOME/.local/bin" -D lychee
Run # Remove the downloaded archive and any unnecessary files after installation
Run /home/runner/work/_actions/lycheeverse/lychee-action/f796c8b7d468feb9b8c0a46da3fac0af6874d374/entrypoint.sh
error: the following required arguments were not provided:
  <inputs>...

Usage: lychee --format <FORMAT> --output <OUTPUT> --user-agent <USER_AGENT> --root-dir <ROOT_DIR> --fallback-extensions <FALLBACK_EXTENSIONS> --github-token <GITHUB_TOKEN> <inputs>...

For more information, try '--help'.

/assign @peppi-lotta
/triage accepted

[tuminoid]

It is also broken for scheduled action: #517

Yet it shows green as successful run. We need to fail the action as well, if it fails like this.

[tuminoid]

It is broken also for PR jobs: https://github.com/metal3-io/metal3-docs/actions/runs/15050233428/job/42335104188?pr=519

 env:
    foundFiles: true
    GITHUB_TOKEN: ***
    INPUT_TOKEN: ***
    INPUT_ARGS: --no-progress
  --github-token
  $(cat changed-files.txt | tr '\n' ' ')
  
    INPUT_DEBUG: false
    INPUT_FAIL: true
    INPUT_FAILIFEMPTY: false
    INPUT_FORMAT: markdown
    INPUT_JOBSUMMARY: true
    INPUT_OUTPUT: lychee/out.md
Error: Network error

Caused by:
    0: error sending request for url (http://code_of_conduct.md/)

This means it inteprets the changed files as URLs, and secondly, the PR does not touch code_of_conduct.md so the list of changed_files.txt is wrong.

@peppi-lotta

[tuminoid]

As seen in #520, the scheduled run now runs, but hits network limitations despite of the GITHUB_TOKEN and also has some weird issues locating stuff.

[tuminoid]

It is also broken for scheduled action: #517

Yet it shows green as successful run. We need to fail the action as well, if it fails like this.

Scheduled action runs after metal3-io/project-infra#1014 but is riddled with rate limiting despite the github_token being supplied, another thing that is not really working.

[tuminoid]

Two issues in PR flow:

1. It checks out the source branch and source main. Source main is years behind, so all files appear changed when compared to PR branch which has been rebased on top of upstream/main
2. Linter considers all files urls, unless prefixes with ./ We need to prefix all of them with ./ and preferably separate them from other arguments with --

[tuminoid]

PR job is still broken after #521 :

[Invalid workflow file: .github/workflows/pr-link-check.yml#L14](https://github.com/metal3-io/metal3-docs/actions/runs/15111850213/workflow)
The workflow is not valid. .github/workflows/pr-link-check.yml (Line: 14, Col: 17): Invalid input, upstream is not defined in the referenced workflow.

[tuminoid]

Fixed by metal3-io/project-infra#1017

/close

[metal3-io-bot]

@tuminoid: Closing this issue.

In response to this:

Fixed by metal3-io/project-infra#1017

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.