From a2d5eb10a3fc8bb6c06af5179c78095ee18e1b6e Mon Sep 17 00:00:00 2001 From: mergify-ci-bot Date: Wed, 9 Sep 2026 10:33:53 +0000 Subject: [PATCH] docs(agent): the buildkite plugin needs a ci-scoped key, which the page did not say --- src/content/docs/integrations/buildkite.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/content/docs/integrations/buildkite.mdx b/src/content/docs/integrations/buildkite.mdx index b49072abcc..49cda17381 100644 --- a/src/content/docs/integrations/buildkite.mdx +++ b/src/content/docs/integrations/buildkite.mdx @@ -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.