Fix: GitHub rate limit

[DanApollo]

Why

Update action is failing due to rate limiting, this is because requests are not authenticated:

See Update #773

What

Unauthenticated requests by worker nodes are rate limited after a small amount of requests. However this can be avoided by authenticating requests Rate Limits for the Rest API

Test

I do not have access to the projects GitHub token, but I tested locally by generating a temporary classic PAT, and running the update script locally like so:

GH_TOKEN=your_token_here npx tsx scripts/commands/sites/update.ts

[freearhey]

The problem is that only 1 request should be sent to the GitHub API, since we only use it to download the currently open issues:

epg/scripts/core/utils.ts

Lines 93 to 102 in 0d8de71

	issues = await octokit.paginate(octokit.rest.issues.listForRepo, {
	owner: OWNER,
	repo: REPO,
	per_page: 100,
	labels,
	state: 'open',
	headers: {
	'X-GitHub-Api-Version': '2022-11-28'
	}
	})

[DanApollo]

The problem is that only 1 request should be sent to the GitHub API, since we only use it to download the currently open issues:

epg/scripts/core/utils.ts

Lines 93 to 102 in 0d8de71

	issues = await octokit.paginate(octokit.rest.issues.listForRepo, {
	owner: OWNER,
	repo: REPO,
	per_page: 100,
	labels,
	state: 'open',
	headers: {
	'X-GitHub-Api-Version': '2022-11-28'
	}
	})

I see, in which case if you would prefer to keep rate limiting, I can close this and instead look into why more than one request is being sent.

[DanApollo]

Looking into this, without an auth token, it looks like the rate limit is shared across requests made within the whole org. I can't find any excessive requests made by any other repositories within the same hour as this job, but I also can't find any evidence that this request was made more than once.

I can only assume the runner was shared with another job that maxed the request limit within the hour.

[freearhey]

I think you're right.

So request authentication is really a good solution in this case.