Conversation
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.
We have a github workflow which checks whether all links on the site are working.
The way this used to be done was that the files themselves were checked for broken links by a tool called lychee, which caused all sorts of issues, because our internal links are mostly generated instead of hardcoded, and lychee didn't know how to interpret the liquid commands which would be "compiled" to links in the actual website.
But lychee can actually just take a real website and check all of its links, so I simply build the site and check the final output of the build 🤓
Also, I found a bunch of broken links, including the one to our bluesky account, which i fixed.