markjaquith / markjaquith/github-pr-slack-copy
GitHub PR HTML monitor failure
Open
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
The scheduled HTML monitor failed for cli/cli.
17 | "User-Agent": "github-pr-slack-copy-monitor",
18 | },
19 | })
20 |
21 | if (!response.ok) {
22 | throw new Error(`GitHub API request failed: ${response.status} ${response.statusText}`)
^
error: GitHub API request failed: 403 rate limit exceeded
at fetchJson (/home/runner/work/github-pr-slack-copy/github-pr-slack-copy/check-github-pr-html.ts:22:13)
::error file=check-github-pr-html.ts,line=22,col=13,title=error: GitHub API request failed%3A 403 rate limit exceeded::%0A at fetchJson (/home/runner/work/github-pr-slack-copy/github-pr-slack-copy/check-github-pr-html.ts:22:13)
Bun v1.4.0 (Linux x64)
Run: https://github.com/markjaquith/github-pr-slack-copy/actions/runs/33174284079
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read check-github-pr-html.ts around fetchJson at line 22, then inspect the linked GitHub Actions run to confirm how the scheduled HTML monitor reaches the 403. Done means the scheduled monitor completes without the reported GitHub API rate-limit failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, github
- Domain
- api, ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100