Workflow Build step fix#1869
Merged
DavidWiseman merged 1 commit intotrimble-oss:mainfrom Apr 27, 2026
Merged
Conversation
Fix issue where build step can fail due to exceeding GitHub API rate limit.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR reduces CI build flakiness caused by unauthenticated GitHub API calls hitting rate limits during the post-build step that fetches the latest serialized-dataset-viewer release metadata.
Changes:
- Add authenticated GitHub API requests (via
GITHUB_TOKEN) and basic retry/backoff logic inPostBuild.ps1. - Pass
GITHUB_TOKENinto the CLI build step across the main CI, release-tag, and variant CI workflows so the post-build script can authenticate.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| DBADashServiceConfig/PostBuild.ps1 | Adds GitHub API request headers (User-Agent + optional Authorization) and retries to reduce transient failures. |
| .github/workflows/tag-create-release.yml | Exposes GITHUB_TOKEN to the CLI build step to avoid unauthenticated rate limiting. |
| .github/workflows/ci_MinimalPermissions.yml | Exposes GITHUB_TOKEN to the CLI build step to avoid unauthenticated rate limiting. |
| .github/workflows/ci_FolderDestination.yml | Exposes GITHUB_TOKEN to the CLI build step to avoid unauthenticated rate limiting. |
| .github/workflows/ci_BucketDestination.yml | Exposes GITHUB_TOKEN to the CLI build step to avoid unauthenticated rate limiting. |
| .github/workflows/ci.yml | Exposes GITHUB_TOKEN to the CLI build step to avoid unauthenticated rate limiting. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+21
to
+25
| } catch { | ||
| if ($attempt -eq $MaxRetries) { throw } | ||
| Write-Warning "GitHub API call failed (attempt $attempt/$MaxRetries): $_. Retrying..." | ||
| Start-Sleep -Seconds (5 * $attempt) | ||
| } |
| break | ||
| } catch { | ||
| if ($attempt -eq $MaxRetries) { throw } | ||
| Write-Warning "GitHub API call failed (attempt $attempt/$MaxRetries): $_. Retrying..." |
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.
Fix issue where build step can fail due to exceeding GitHub API rate limit.