sync-shared-config: use deterministic backoff#460
Merged
Conversation
We can use `strategy.job-index` [1] to help to determine the backoff time for each job in the matrix. This will help to arrange the jobs in the matrix more deterministically and efficiently than using a random backoff, while still avoiding hitting rate limits. [1]: https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#strategy-context
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the sync-shared-config workflow to replace randomized request staggering with a deterministic backoff derived from the matrix job index, aiming to reduce API/rate-limit collisions more predictably.
Changes:
- Replace random sleep-based staggering with a deterministic delay based on
strategy.job-index. - Expose the matrix job index to the step via
JOB_INDEXenv var.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We can use
strategy.job-index1 to help to determine the backoff time for each job in the matrix. This will help to arrange the jobs in the matrix more deterministically and efficiently than using a random backoff, while still avoiding hitting rate limits.Footnotes
https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#strategy-context ↩