Skip to content

Add link checker to fix broken links in markdown#140

Open
farazmd wants to merge 1 commit intokubernetes-sigs:mainfrom
farazmd:link-checker
Open

Add link checker to fix broken links in markdown#140
farazmd wants to merge 1 commit intokubernetes-sigs:mainfrom
farazmd:link-checker

Conversation

@farazmd
Copy link

@farazmd farazmd commented Feb 27, 2026

Description

Added link checker (lychee) to check for broken links in markdown files as part of the verify process.
Also fixed broken links in README.md and docs/book/src/introduction.md

Related Issue

Fixes #137

Type of Change

/kind feature

Testing

Running make verify - runs the verify-links.sh script

Checklist

  • [ x ] make test passes
  • [ x ] make lint passes

Does this PR introduce a user-facing change?

NONE

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 27, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: farazmd
Once this PR has been reviewed and has the lgtm label, please assign sergeykanzhelev for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@netlify
Copy link

netlify bot commented Feb 27, 2026

Deploy Preview for node-readiness-controller ready!

Name Link
🔨 Latest commit d335a82
🔍 Latest deploy log https://app.netlify.com/projects/node-readiness-controller/deploys/69a1c89a87c78c000881ff84
😎 Deploy Preview https://deploy-preview-140--node-readiness-controller.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 27, 2026
@k8s-ci-robot
Copy link
Contributor

Welcome @farazmd!

It looks like this is your first PR to kubernetes-sigs/node-readiness-controller 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/node-readiness-controller has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Feb 27, 2026
@k8s-ci-robot
Copy link
Contributor

Hi @farazmd. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Feb 27, 2026
@ajaysundark ajaysundark requested review from Priyankasaggu11929 and ajaysundark and removed request for SergeyKanzhelev and tallclair February 27, 2026 17:23
darwin-arm64)
LYCHEE_BASENAME="${LYCHEE_BINARY}-arm64-macos"
;;
windows-amd64)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a static lychee binary (built with musl maybe) that we can use for windows-amd64 case (if we are adding it?)
There's also lychee-x86_64-windows.exe in the artifacts.

But overall, I feel like, rather than skipping check for windows-amd64, it should be flagged as unsupported platform in our controller case.


# Remove artifacts
rm -rf /tmp/${LYCHEE_BINARY}.${EXT}
rm -rf /tmp/docs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rm -rf /tmp/docs

where are these coming from ^?

rm -rf /tmp/docs

# Change back to root directory
cd "$ROOT_DIR"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +58 to +64
LYCHEE_URL="https://github.com/lycheeverse/lychee/releases/download/lychee-v${LYCHEE_VERSION}/${LYCHEE_BASENAME}.${EXT}"

echo "downloading ${LYCHEE_BASENAME}.${EXT} from ${LYCHEE_URL}"
set -x
curl -fL -o /tmp/${LYCHEE_BINARY}.${EXT} "${LYCHEE_URL}"

${EXTRACT_CMD} "/tmp/${LYCHEE_BINARY}.${EXT}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's wrap the binary downloading and extracting with error handling

LYCHEE_URL="https://github.com/lycheeverse/lychee/releases/download/lychee-v${LYCHEE_VERSION}/${LYCHEE_BASENAME}.${EXT}"

echo "downloading ${LYCHEE_BASENAME}.${EXT} from ${LYCHEE_URL}"
set -x
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think set -x is not needed in the middle of the script

@Priyankasaggu11929
Copy link
Member

/ok-to-test

@farazmd, thanks for the PR. I have left a few in-line comments, and dropping some suggestions below as well.

Let's create a temp dir in the beginning of the verify-link script and do a cleanup with trap rather than us manually catching and cleaning up every single artifact

TEMP_DIR=$(mktemp -d)
trap 'rm -rf "${TEMP_DIR}"' EXIT

Also, let's add a .lycheeignore file to ignore links like example.com or localhost etc

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Feb 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: Add automated link checker to 'make verify'

3 participants