Open
Conversation
When both status-job and capture-job-durations were set the action paginated listJobsForWorkflowRun twice — once to find the status job, once to emit per-job duration events. Fetch jobs into a single array up front and reuse it for both, halving GitHub API calls per run on workloads that use both features. No behavior change otherwise.
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
1 participant
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.
When both
status-jobandcapture-job-durationsare set, the action was paginatinglistJobsForWorkflowRuntwice — once to find the status job, once to emit per-job duration events. Fetch jobs into a single array up front and reuse it, halving GitHub API calls per run for callers using both features.Why bother
Heavy CI users (e.g. posthog/posthog runs the action twice per workflow with both features on, against a dedicated GitHub App token) burn a couple hundred extra requests/hour for no reason. Not currently rate-limited, but easy win.
Behavior
No functional change. Same events emitted, same warning when status job is missing.