-
Notifications
You must be signed in to change notification settings - Fork 394
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
GitHub Actions link checker #1619
Conversation
This is my attempt to rig up our link checker to run on GitHub Actions after the deployment is finished. Boy howdy do I hope this can be tested in a deploy preview.
Seems like PR workflows do show up. Nice! No need for prod testing. |
This time I read the payload docs more carefully
I think this could be causing a bug with GH actions
Seems there's no way around needing the deployment trigger, even if the job is skipped on deployment. The prefix can't be removed, but "Run" and "Report" are the most evocative names I can think of for the suffixes
Here's a copy of the latest changes!
|
…-actions-link-check
GitHub Actions Link Checker
This PR introduces a big feature overhaul: A completely new JS-based link checker that runs in both GitHub Actions and the CLI!
You can find the new app's repo at https://github.com/iterative/link-check. It has a submodule for distributing the lambda-esque compiled action, but the source is all in the same repo.
This link checker primarily aims to solve two issues:
These two features, if I understand correctly, make this PR fix #1000 barring any regressions
Output examples
Failing deploy check with various common reasons
Successful deploy check
Sitewide check reporting unused link patterns
Full check with all patterns used