The GitHubMergePR check fails for being rate limited
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 109
- Forks
- 85
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 1
Description
As reported in https://github.com/dotnet/roslyn-tools/pull/1086#issuecomment-916512729.
PRs to roslyn-tools have a non-required check that the GitHubMergePR pipeline will still run with the included changes. This check often fails due to being rate limited on making GitHub requests.
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
Start with the linked roslyn-tools pull request and its issue comment, then inspect the GitHubMergePR pipeline and the GitHub requests it makes. Reproduce or trace the rate-limit failure and document the relevant request path. Done means the non-required check no longer fails solely because GitHub requests are rate limited.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, github
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100