-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 Add task to update link checker base branch #9208
📖 Add task to update link checker base branch #9208
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kubernetes-sigs/cluster-api-release-team
Not sure if this should be added to the checklist of tasks.
Signed-off-by: killianmuldoon <kmuldoon@vmware.com>
93d075d
to
1fff665
Compare
We need to do something similar on CAPV - and change the base_branch listed in the older branches. |
/lgtm /hold Change is fine for now. Would be good if this action could auto-discover the base branch. (or simply look at the delta in the PR). But this can be a follow-up. Feel free to unhold |
LGTM label has been added. Git tree hash: d42739f883da2f6c779a4dce4301e96f0fb6490c
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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:
Approvers can indicate their approval by writing |
/hold cancel |
Doesn't look like the capability exists for this action: https://github.com/gaurav-nelson/github-action-markdown-link-check#check-only-modified-files-in-a-pull-request We could disable the PR link checker entirely for older branches as it's not really that useful there, but that's as much work as updating the branch and requires a bit of explanation besides. |
Alright. Thx for looking it up. Then let's go with manually updating the branch |
Thank you very much for taking care of this! Please follow-up with the same for CAPV. |
/cherry-pick release-1.5 |
/cherry-pick release-1.4 |
@sbueringer: #9208 failed to apply on top of branch "release-1.5":
In response to this:
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: #9208 failed to apply on top of branch "release-1.4":
In response to this:
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. |
No need to cherry-pick release docs back IMO - I don't think it's worth the effort to keep them in sync. |
Agree, I tried it for the fix of the broken link. |
Add a task to update the base branch in our PR markdown link checking action when creating a new release branch.
/area release