-
Notifications
You must be signed in to change notification settings - Fork 317
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
Absolute paths for link checker and baseURL #1369
Conversation
Hello @klieret, cc @graeme-a-stewart and @hegner for website enhancements. I see this long-standing PR. It's rather short. Do you intend to finalise or else we close at this point? |
Hello @klieret, what is the status here? Let me also ping @graeme-a-stewart and @hegner since they are thinking about the new revamped site. |
Is this PR still relevant? I have the feeling that yes and it would be a good idea not to hardcode the host name of the web site? If yes, why we don't merge this PR is @klieret is not available to follow it up? |
Probably. I'm no expert but the changes seem small eough that somebody can review? |
I can take a look, but I would say this wants a rebase first! |
fa210d4
to
b9cc6b9
Compare
The full check takes way too long and can result in false positives as well (full checks are what made the old link checker unusable in the end).
OK, this all looks good to me. Killian had set it to link check the whole site, but that took about an hour and we used to get badly burned by false positives when that was done on PRs. So I have reverted to the check of changed pages only. (It would be good to also have a workflow that triggers a whole site check, but that shouldn't be the normal workflow for PRs.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for this change @klieret!
In reference to #1046