semantic-release / semantic-release/github
Request quota exhausted causes GH Action to hang
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 534
- Forks
- 150
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
Hi,
I'm running semantic-release as a part of our deployment workflow, and finally got it configured, but when it runs it hangs while searching for issues. This is the first run so if it's trying to find an issue for each commit it found since the previous release (never), it's going to have a lot to check.
We don't even use issues in Github, so the optimal solution would be a config setting to skip searching for issues altogether.
[...]
[1:23:38 PM] [semantic-release] › ✔ Created tag v1.0.0-beta.1
[1:23:38 PM] [semantic-release] › ℹ Start step "publish" of plugin "@semantic-release/github"
[1:23:38 PM] [semantic-release] [@semantic-release/github] › ℹ Published GitHub release: https://github.com/myorg/myrepo/releases/tag/v1.0.0-beta.1
[1:23:38 PM] [semantic-release] › ✔ Completed step "publish" of plugin "@semantic-release/github"
[1:23:38 PM] [semantic-release] › ℹ Start step "success" of plugin "@semantic-release/github"
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
Request quota exhausted for request GET /search/issues
[...]
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
The reported path is the @semantic-release/github success step, where GET /search/issues repeats after publishing a release. Start by tracing that search and the plugin configuration; done means an explicit setting can skip issue searching and the quota-exhaustion case no longer hangs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100