-
Notifications
You must be signed in to change notification settings - Fork 406
test: links: fix failures #997
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
Conversation
|
What's the logic behind the sorting? |
|
er just piped though |
|
yay re-ran daily and succeeded: https://app.circleci.com/jobs/github/iterative/dvc.org/2292 |
|
I'm thinking if we should create an exclusion list on file level? (don't analyze tests?). To avoid adding a lot of links to the existing file? what do you think @casperdcl @jorgeorpinel ? |
|
Well we could do comments both in js and markdown similar to |
|
You mean this sort of thing? [md]http://dead.link <!-- noqa -->'http://dead/link' // noqa |
|
more like specify somewhere that I would like to exclude |
Yes, only certain js and the md files really matter here, so I would even make it a white list with a pattern to match (similar to what Would also be nice if these files can ignore
|
dailyworkflow builds on https://circleci.com/gh/iterative/dvc.org (e.g. https://circleci.com/gh/iterative/dvc.org/2264) for an up-to-date listexclude-links.txtexclude-links.txt0xx,3xxetc) be counted as errors instead?