Open MadVikingGod opened 2 years ago
+1 for an unscoped min-permissioned token.
The link checker is failing due to not having some identity associated with the request: https://github.com/open-telemetry/opentelemetry-go/actions/runs/3969987815/jobs/6805174715
The link in question, https://github.com/open-telemetry/opentelemetry-go/projects, succeeds for me when I make the request as my user. But when I make the request anonymously, I reproduce the error (500) mentioned in the workflow.
I think this both motivates us to start using an access token, but it also points out that by doing so we might miss issues for users not logged into GitHub.
The link checker is failing due to not having some identity associated with the request: https://github.com/open-telemetry/opentelemetry-go/actions/runs/3969987815/jobs/6805174715
The link in question, https://github.com/open-telemetry/opentelemetry-go/projects, succeeds for me when I make the request as my user. But when I make the request anonymously, I reproduce the error (500) mentioned in the workflow.
I think this both motivates us to start using an access token, but it also points out that by doing so we might miss issues for users not logged into GitHub.
We should see if the TC can open a support case for this.
Interim solution is to ignore this in the link checker.
Interim solution is to ignore this in the link checker.
https://github.com/open-telemetry/opentelemetry-go/pull/3620
Description
We seem to have too many links to check all at once, and we are only increasing with our changelog. I found this when adding an issue template, with 7 links to github. We are very close to the limits
Environment
Steps To Reproduce
Links (Fail Fast) / check-links (pull_request)
runsExpected behavior
This step should not fail.
Possible solutions
like https://github.com/open-telemetry/opentelemetry-go/releases/tag/.*
. This represents one class of growing links, every release creates a new one, and is also a large number of links we check.