🌱 Split MD link checker into periodic and PR focused

[killianmuldoon]

Signed-off-by: killianmuldoon [email protected]

This PR changes the MD link checker action to only work on files modified by the PR. This will hopefully reduce disruption from MD link checker flakes on PRs. This commit also adds a periodic link-checker action that should scan all MDs on a weekly schedule and identify broken links across the repo more widely.

[killianmuldoon]

I don't think we need branches here, but I'm not sure if this will actually scan every branch on the repo (that could be a good thing to pick up broken links in older versions of the book)

[killianmuldoon]

/hold

Still figuring out the right syntax for the cronjob.

[killianmuldoon]

/remove-hold

This should run weekly on a Thursday once merged.

[chrischdi]

/lgtm

Great idea 👍

How do we get notified for a failing weekly gh action? Normally we track this via testgrid which is obviously not possible using gh actions I think?!

[killianmuldoon]

How do we get notified for a failing weekly gh action? Normally we track this via testgrid which is obviously not possible using gh actions I think?!

I think we'll get a notification (if you have failing actions turned on in github notifications)

[sbueringer]

How do we get notified for a failing weekly gh action? Normally we track this via testgrid which is obviously not possible using gh actions I think?!

I think we'll get a notification (if you have failing actions turned on in github notifications)

Yup we should.

[sbueringer]

/lgtm

/cherry-pick release-1.2

(the link to microsoft.com is just too flaky to not cherry-pick into all supported releases)

Thx @killianmuldoon !

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.2 in a new PR and assign it to you.

In response to this:

/lgtm

/cherry-pick release-1.2
/cherry-pick release-1.1

(the link to microsoft.com is just too flaky to not cherry-pick into all supported releases)

Thx @killianmuldoon !

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/test-infra repository.

[sbueringer]

/cherry-pick release-1.1

[k8s-infra-cherrypick-robot]

@sbueringer: once the present PR merges, I will cherry-pick it on top of release-1.1 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.1

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/test-infra repository.

[vincepri]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vincepri

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vincepri]

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

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6869

In response to this:

/cherry-pick release-1.1

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/test-infra repository.

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #6870

In response to this:

/lgtm

/cherry-pick release-1.2

(the link to microsoft.com is just too flaky to not cherry-pick into all supported releases)

Thx @killianmuldoon !

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/test-infra repository.