Repository navigation
Create link_checker.yml - #465
Merged
Merged
Conversation
Adds a github workflow that builds the site and checks links anytime a PR wants to change a markdown file.
Merged
j---
approved these changes
Feb 15, 2024
j---
left a comment
Collaborator
There was a problem hiding this comment.
I'm so glad this will solve issue 404.
This was referenced Feb 15, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a github workflow that builds the site and checks links anytime a PR wants to change a markdown file.
I feel obligated to acknowledge the entirely unintentional fact that issue #404 is the absolute best issue number possible for that specific issue.
This PR is a direct follow-on to
and should be merged immediately after #443 is merged. Rationale: #443 puts the content in a known-good state with no broken links that
linkcheckercan find. So if we add this workflow immediately afterwards, we can ensure that we keep it that way going forward. Merging this PR before #443 would just leave us with a failing workflow because there are a lot of broken links in the markdown up to that point.