-
Notifications
You must be signed in to change notification settings - Fork 76
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
False positives #50
Comments
Update, the failures went away when I linked to https://substrate.dev instead of just substrate.dev I'll leave the issue open because either:
|
I think, it is not easily possible to detect that GitHub Flavored Markdown only supports autolinking when the text starts with Maybe, if links start with |
Good to know about those autolinks. Thanks for showing me that. But the links in my repo that were reported borken were not auto-linked. They were linked explicitly like I'm not stuck anymore, so close this if you like the way it works, but it seems like an issue to me. |
I think this issue deal more with how https://github.com/tcort/markdown-link-check handles the links. Glad that you found a way around to fix those links. I am closing this issue as it doesn't directly relate to the GitHub action. |
this CI job is failing becuase broken links are reported. In reality the links are working.
The text was updated successfully, but these errors were encountered: