Skip to content
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

Meta: can we fix the link checker? #916

Open
tobie opened this issue Jul 19, 2022 · 12 comments
Open

Meta: can we fix the link checker? #916

tobie opened this issue Jul 19, 2022 · 12 comments
Labels
waiting-on-pull-request There's agreement as to what needs to happen, now someone has to do it.

Comments

@tobie
Copy link
Contributor

tobie commented Jul 19, 2022

Currently the link checker fails a number of pull requests for broken links that aren't created by the PR its.f/

Could we either:

  • fix it so it only fails links relevant to the PR itself,
  • have a process and/or someone in charge of fixing broken links, or
  • remove it altogether?
@ljharb
Copy link
Member

ljharb commented Jul 19, 2022

The second option is typically what’s done - someone has to fix the links in main.

An alternative would be to run it in a cron, instead of on PRs.

@joesepi
Copy link
Member

joesepi commented Jul 19, 2022

I like the cron option.

@bnb
Copy link
Member

bnb commented Jul 19, 2022

Generally in the situation where it's failing, I'd hope we'd not block on that and also open a PR or Issue (even a small one) to note the failure and address it separately :)

AFAIK I don't think the first one is possible with the existing setup. Also, it does currently run on a cron and can be manually run if needed but given that nobody here's aware of that it might not be a good strategy to actually get the issues solved.

@tobie
Copy link
Contributor Author

tobie commented Jul 19, 2022

Generally in the situation where it's failing, I'd hope we'd not block on that and also open a PR or Issue (even a small one) to note the failure and address it separately :)

Agreed. The cognitive overhead is real, though.

@bnb
Copy link
Member

bnb commented Jul 19, 2022

I really wish GitHub provided a mechanism to mark a check as optional in Actions (it was possible in v1, but not v2 unfortunately)

@ljharb
Copy link
Member

ljharb commented Jul 19, 2022

What do you mean optional - everything's optional unless the branch protections mark it as required, no?

@bnb
Copy link
Member

bnb commented Jul 19, 2022

GitHub Actions v1 and GitHub Apps have a third, neutral state that's not pass/fail. GitHub Actions v2 does not (there's an issue that's been open for years and the SDK docs said it's an upcoming feature for just as long IIRC).

@ljharb
Copy link
Member

ljharb commented Jul 19, 2022

oh woof, that's a real shame it's not well-supported :-/

@bnb
Copy link
Member

bnb commented Aug 2, 2022

it's fixed :)

@joesepi joesepi closed this as completed Aug 2, 2022
@bnb
Copy link
Member

bnb commented Aug 2, 2022

refs: #918 #917

@tobie tobie reopened this Apr 26, 2023
@tobie
Copy link
Contributor Author

tobie commented Apr 26, 2023

This is again showing up as an issue in pull requests.

The link that's triggering the linter is mistakenly (?) returning 403 despite actually working properly:

curl -I https://thenewstack.io/why-outdated-jquery-is-still-the-dominant-javascript-library/
HTTP/2 403 
date: Wed, 26 Apr 2023 07:28:28 GMT
content-type: text/html; charset=UTF-8
cross-origin-embedder-policy: require-corp
cross-origin-opener-policy: same-origin
cross-origin-resource-policy: same-origin
permissions-policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=()
referrer-policy: same-origin
x-frame-options: SAMEORIGIN
cf-mitigated: challenge
cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
expires: Thu, 01 Jan 1970 00:00:01 GMT
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=Y1zUwpBpel8FXK3odvLylazC0gmKUJcWXQT5GFtaTe78T0Z65GDpbUkKYw8Chk4nu9jZcuTWEkYs22MkpyuTQKoLMcGCTb%2FWgbqkF%2FivM%2Bbddrgoyvh6GQLa0L%2BBtJQl"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
server: cloudflare
cf-ray: 7bdd1bef5f2c5a25-MXP
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400

Can we just kill this thing until we have a solution that doesn't interfere with day to day operations?

@joesepi
Copy link
Member

joesepi commented May 23, 2023

Jordan is making link checker non blocking on PRs.

Still would be good to get it on a cron schedule

@tobie tobie added waiting-on-pull-request There's agreement as to what needs to happen, now someone has to do it. and removed cross-project-council-agenda labels May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting-on-pull-request There's agreement as to what needs to happen, now someone has to do it.
Projects
None yet
Development

No branches or pull requests

4 participants