Skip to content

docs(agent): the buildkite plugin needs a ci-scoped key, which the page did not say #12749

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mergify merged 1 commit into from
Sep 9, 2026
Merged

docs(agent): the buildkite plugin needs a ci-scoped key, which the page did not say #12749

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions src/content/docs/integrations/buildkite.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -132,8 +132,9 @@ steps:
command: .buildkite/dynamic-pipeline.sh | buildkite-agent pipeline upload
```

The plugin reads your [application key](/api/usage) from `MERGIFY_TOKEN` in
the agent's environment. Detection is local, so the meta-data this step writes,
The plugin reads your application key from `MERGIFY_TOKEN` in the agent's
environment. It needs the [`ci` scope](/api/usage#application-key-scopes); an
`admin` key is rejected. Detection is local, so the meta-data this step writes,
and the step skipping below that reads it, work without a token. What a missing
token costs is the upload: the plugin logs a warning and sends nothing, so the
merge queue never sees the scopes.
Expand Down