bevyengine / bevyengine/bevy-website

Add exponential back-off retrying for the github API tools in `generate-release`

Open
#1,317 0 comments 0 reactions 0 assignees View on GitHub
C-Automation C-Feature S-Ready-For-Implementation
Dominant language
JavaScript
Stars
249
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
6

Description

When using the various methods to interact with Github's API, it's possible to get rate-limited. This is particularly common with the various mutating operations, like opening issues or leaving comments.

Rather than simply aborting due to failure, we should retry, using the standard exponential back-off strategy, up to a max time.

This will make the tool much more reliable to run automatically.

Contributor guide

Open the contributing guide

Research direction

Start at the generate-release entry point and locate the methods that interact with GitHub's API, especially mutating operations such as opening issues or leaving comments. Run the existing generate-release workflow and verify that rate-limit failures retry with exponential back-off and stop at a defined maximum time instead of aborting immediately.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, javascript
Domain
release, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.