-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update mdtoc, fix TOC entries with backticks #4437
Conversation
v1.1.0 (which is 3 years old, but only 1 commit newer than what we're currently using) correctly handles headings with backticked elements.
/assign @mrbobbytables |
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.
Thanks!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danwinship, mrbobbytables 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 |
The version of mdtoc currently used by
update-toc.sh
/verify-toc.sh
does not handle headings with backticks in them, resulting in broken links in some KEPs. eg, in the nftables kube-proxy KEP, the table of contents entry for the##### Forcing traffic on `HealthCheckNodePort`s to be accepted
heading links to#forcing-traffic-on-s-to-be-accepted
but the actual anchor generated by GitHub is#forcing-traffic-on-healthchecknodeports-to-be-accepted
.This has actually been fixed in https://github.com/kubernetes-sigs/mdtoc for a very long time, we're just still using a very old version of mdtoc...
cc @saschagrunert