-
Notifications
You must be signed in to change notification settings - Fork 167
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
Comments
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. |
I like the cron option. |
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. |
Agreed. The cognitive overhead is real, though. |
I really wish GitHub provided a mechanism to mark a check as optional in Actions (it was possible in v1, but not v2 unfortunately) |
What do you mean optional - everything's optional unless the branch protections mark it as required, no? |
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). |
oh woof, that's a real shame it's not well-supported :-/ |
it's fixed :) |
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:
Can we just kill this thing until we have a solution that doesn't interfere with day to day operations? |
Jordan is making link checker non blocking on PRs. Still would be good to get it on a cron schedule |
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:
The text was updated successfully, but these errors were encountered: