Repository navigation
Conversation
Record pinned native GitHub evidence and the unreleased buildkite-gha support with explicit offline and expression-position limits. Amp-Thread-ID: https://ampcode.com/threads/T-55f7b774-50aa-497e-a379-7a39c0cfed07 Co-authored-by: Amp <amp@ampcode.com>
github-actions
Bot
added
the
pipelines
![buildsworth-bk-app[bot]](https://avatars.githubusercontent.com/in/3010600?s=60&v=4){kind=small}
sj26
enabled auto-merge (squash)
October 21, 2026 04:17
Contributor
|
Closing in favor of the internal version. |
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.
Why
buildkite-gha#613 adds hosted support for build-scoped workflow concurrency:
The compatibility reference needs to distinguish that exception from other import-time fields.
What
Document the Buildkite build-ID mapping, stable per-build groups, explicit offline errors, and unchanged limits. Mark this support as unreleased; no package release is part of these PRs.
Record the successful native GitHub run, its pinned fixture, and the limits of that evidence.
Related: PB-3721.