-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Markdown link check has an issue with some links even though they work fine #5872
Comments
[Triage] There are configuration options that we could use here:
|
Another issue I just noticed is 429s when validating the Docker Hub links 😞. |
[Triage] Instead of the GitHub READMEs pointing to DockerHub repos, we should make them point to the other GitHub READMEs instead. Since there's no extra content on DH that isn't in our GH readmes, there's not much point in linking there from here. That would remove this entire class of issues. |
[Triage] The original issue described in the post was resolved with #5892, so this can be closed. Any additional work should be filed as a separate issue. |
I found several more instances of this, all on microsoft.com links: https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-linux
https://docs.microsoft.com/virtualization/windowscontainers/images-eula
https://learn.microsoft.com/dotnet/core/deploying/ready-to-run
https://learn.microsoft.com/dotnet/api/system.security.cryptography.x509certificates.storelocation
The author of the markdown link checker recommends their new project, UmbrellaDocs/action-linkspector, instead. Development has stopped on the current markdown link checker (source). Of note, the new checker does support running as a Docker image. |
I have noticed that the markdown link check Github action has issues with certain links, even though the links work correctly.
Both of the links Work On My Machine. This has been causing many valid PRs to appear as failing validation. I believe that retries have caused some of these to pass but I cannot confirm that.
Related: #5818
/cc @MichaelSimons
The text was updated successfully, but these errors were encountered: