Closed nathany closed 7 months ago
Thanks for flagging the broken links.
I'd be cautious of validating links via GitHub action. Links to other websites may break independent of a given commit to Carbon. However, failing actions would form a barrier to commits, and creating a barrier because a commit happens to touch a file that previously had a broken link may be discouraging.
Description of the bug:
This is the result of running the lychee link checker against the markdown files.
Link to documentation:
https://github.com/carbon-language/carbon-lang
What should it say instead?
No response
Any other information, logs, or outputs that you want to share?
This is what I was thinking:
Separately from that PR, I could run lychee against the Wiki and open a separate issue.
We could consider adding a link checker to CI if the false positives can be resolved (I could just add --accept 429, but that's not entirely ideal). Lychee has a GitHub Action, but I'm not sure if/how to integrate it with pre-commit.