Deprecation Notice: Replace deprecated `gaurav-nelson/github-action-markdown-link-check`

[Okabe-Junya]

Background

About two weeks ago, gaurav-nelson/github-action-markdown-link-check was marked as deprecated:

cf. https://github.com/gaurav-nelson/github-action-markdown-link-check

This repository is now ⛔️ deprecated and is no longer actively maintained.
For support and further development, please use the maintained fork available at Tcort GitHub Action Markdown Link Check.

Since this repository currently uses gaurav-nelson/github-action-markdown-link-check, we need to clean it up appropriately.

cluster-api-provider-vsphere/.github/workflows/pr-md-link-check.yaml

Line 18 in 7b1a146

- uses: gaurav-nelson/github-action-markdown-link-check@3c3b66f1f7d0900e37b71eca45b63ea9eedfce31 # tag=1.0.17

cluster-api-provider-vsphere/.github/workflows/weekly-md-link-check.yaml

Line 23 in 7b1a146

- uses: gaurav-nelson/github-action-markdown-link-check@3c3b66f1f7d0900e37b71eca45b63ea9eedfce31 # tag=1.0.17

While the forked at tcort/github-action-markdown-link-check is suggested, it may still be too early to rely on that action.

Question:

How should we handle this deprecation in our workflow?

/kind cleanup

[Okabe-Junya]

xref

• Deprecation Notice: Replace deprecated gaurav-nelson/github-action-markdown-link-check cluster-api#12138
• Deprecation Notice: Replace deprecated gaurav-nelson/github-action-markdown-link-check cluster-api-provider-azure#5598

[Okabe-Junya]

/area ci

[k8s-ci-robot]

@Okabe-Junya: The label(s) area/ci cannot be applied, because the repository doesn't have them.

In response to this:

/area ci

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-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[sbueringer]

/remove-lifecycle stale
/lifecycle frozen