-
-
Notifications
You must be signed in to change notification settings - Fork 386
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
Various fixes for awesome.md
#4448
Conversation
pat-s
commented
Nov 23, 2024
- git.rustybever cannot be reached. Might be temporary
- wording updates
Deployment of preview was torn down |
Not sure how we want to handle (temp) unavailable resources. |
Co-authored-by: Robert Kaussow <mail@thegeeklab.de>
Maybe having a waiting period for ~ 3 days makes sense? It surely differs for the domain at hand, e.g. I'd expect a git.something to be back earlier than a random personal website domain. |
Assumptions aside we should find a generic rule. I would wait at least a week. |
The problem is that within that week all CI checks will fail without any action. And this causes interruption for automated processed and also takes developer time looking at runs and causes unneeded discussions about the failure per se. |
Move linkchecking of communit resources to a dedicated workflow as we do for security scanning and make it not required. |
Good ideas overall. The check is already optional. To not block this PR due to this, I've added the resources again, so this PR is not blocked by this discussion. |