-
Notifications
You must be signed in to change notification settings - Fork 145
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
WIP: urlchecker github action #591
base: develop
Are you sure you want to change the base?
Conversation
@boegel this should work once approved and added to easybuilders project from marketplace https://github.com/marketplace/actions/urls-checker |
Invoke action on develop,master upon PR and only on push to master branch. Since most documentation will get merged to develop first, it makes no sense to check a PR to master branch. Its only in case if push is directed to master branch directly without going through develop first.
Sorry I didn't mean to do that! |
IMO this is way too slow, we need to be able to whitelist all of our repo links and only check external links. From the docs, it doesn't look like white-listing |
I tell a lie, it is possible... |
Note that this clones the repo and doesn't take a branch as an option, so can only do something useful on a push to master. Also, it can't deal with our templating ( |
FWIW Our templating is a real problem with this and the urlchecker crashes with some of our URLs:
|
@ocaisa i have submitted a ticket to developer for feedback urlstechie/urlchecker-action#7. |
@ocaisa even if this URL-checker may not be merged due to some of the issues. I think going through the report of all invalid URLs and fixing them first would be one major improvement. For end-user reading documentation and coming through a broken link can be problematic. |
@boegel and @ocaisa the github action has changed its now https://github.com/urlstechie/urlchecker-action which is reimplementation of the one I sent you. I think you can setup filter on what files to check or exclude. Anyhow I am happy to help resolve this old PR by refactoring this or we can close this PR. |
No description provided.