-
Notifications
You must be signed in to change notification settings - Fork 29
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
Implement link checking workflow #46
Comments
MarcSWD
moved this from 🗄 Backlog
to SPR-2 | 30/01 - 10/02
in web.dev & DCC: Sprint board with Tokyo
Jan 25, 2023
matthiasrohmer
moved this from SPR-2 | 30/01 - 10/02
to 🚧 In Progress
in web.dev & DCC: Sprint board with Tokyo
Feb 10, 2023
matthiasrohmer
moved this from 🚧 In Progress
to 🛎 To Do
in web.dev & DCC: Sprint board with Tokyo
Feb 10, 2023
Estimate for dev = 8 days (SPR-3) |
Blazzike
moved this from 🛎 To Do
to 🧐 In Review
in web.dev & DCC: Sprint board with Tokyo
Feb 17, 2023
Blazzike
moved this from 🧐 In Review
to 🛎 To Do
in web.dev & DCC: Sprint board with Tokyo
Feb 20, 2023
matthiasrohmer
moved this from 🛎 To Do
to 🚧 In Progress
in web.dev & DCC: Sprint board with Tokyo
Feb 22, 2023
Blazzike
moved this from 🚧 In Progress
to 🧐 In Review
in web.dev & DCC: Sprint board with Tokyo
Mar 20, 2023
awaiting PR review: GoogleChrome/developer.chrome.com#5667 |
spoke with Matthias, he's waiting on internal updates prior to marking this one as 'done' |
Blazzike
moved this from 🧐 In Review
to 🛎 To Do
in web.dev & DCC: Sprint board with Tokyo
May 4, 2023
Blazzike
moved this from 🛎 To Do
to 🚧 In Progress
in web.dev & DCC: Sprint board with Tokyo
May 4, 2023
Blazzike
moved this from 🚧 In Progress
to 🧐 In Review
in web.dev & DCC: Sprint board with Tokyo
May 4, 2023
.editorconfig |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Part of #45. Implement a link checking workflow, that checks for broken links on a page. Ideally the tool only runs on the changed page in a PR (to safe time and prevent positives on files unrelated to the PR) but is also able to check the full site - ideally not statically but served via our own express app.
As mentioned in #45, the problem spans wider than just broken links: we also want to make sure every page we generate is also discoverable (say linked, see GoogleChrome/developer.chrome.com#83) on the site and we also want to make sure our external sources are not broken.
The text was updated successfully, but these errors were encountered: