docs(agent): the buildkite plugin needs a ci-scoped key, which the page did not say - #12749
Merged
Conversation
Contributor
Merge Protections🟠 1 of 6 protections blocking · waiting on 🤖 CI
🟠 🤖 Continuous IntegrationWaiting for
Waiting checks:
|
sileht
approved these changes
Sep 9, 2026
jd
approved these changes
Sep 9, 2026
Contributor
Merge Queue Status
This pull request spent 6 minutes 8 seconds in the queue, including 3 minutes 36 seconds running CI. Required conditions to merge
|
63 tasks
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.
The page told readers the plugin reads "your application key" from
MERGIFY_TOKEN, without saying which scope that key needs. Application keyscarry one of two scopes and the scopes-upload endpoints accept only
ci; anadminkey is rejected. A reader who picks the more powerful-sounding scopegets a plugin that detects scopes correctly, writes its meta-data correctly,
skips the right steps, and then fails to upload — which is the one part of the
chain the merge queue actually consumes.
The omission is worth closing now rather than later because the Terraform page
gained the opposite instruction in the same change: its provider needs an
adminkey, and it says so. A reader holding one key and reading both pages hadnothing to tell them the two integrations want different scopes.
The sentence now names the
ciscope and links the scopes reference, in thesame form
merge-queue/scopes.mdxalready uses for the equivalent REST call.Nothing else on the page changes; the surrounding explanation of what a missing
token costs was already correct.
Evidence: the security scheme the scopes endpoints declare in the API schema,
and the published scope table for application keys.