SSWConsulting / SSWConsulting/SSW.Rules
🐛 GitHub API Rate Limit Breaks Deploy triggers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Cc: @bradystroud @adamcogan @wicksipedia
Hi @BrookJeynes
Describe the Bug
When an AzureDevOps deploy is triggered via the SSW.Rules.Content GitHub Action, it may not work due to GitHub API Rate Limits
To Reproduce
- Trigger a build of rules (may be sporadic)
Expected Behavior
Build + deploy is triggered in Azure DevOps
Tasks
- Investigate
- Fix
More Information
Screenshots
Figure: The error
Thanks!
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 by locating the SSW.Rules.Content GitHub Action entry point and the code that triggers the Azure DevOps deploy. Reproduce the sporadic rules build, inspect the screenshot's rate-limit error, and determine how the action handles GitHub API limits. Done means builds reliably trigger the expected Azure DevOps deployment without exceeding or mishandling the API limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, typescript
- Domain
- ci-cd, cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100