[Feat] Add Buildkite built-in integration - #2994
Merged
Merged
Conversation
Contributor
|
No new code issues found. See task
Reviewed 89ed506 |
This was referenced Sep 19, 2026
roomote-roomote
Bot
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
September 19, 2026 20:26
daniel-lxs
approved these changes
Sep 19, 2026
daniel-lxs
approved these changes
Sep 19, 2026
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.
What changed
MCP_INTEGRATIONSregistry using the provider-enforcedhttps://mcp.buildkite.com/mcp/readonlyendpoint, deployment-scoped OAuth/DCR, the exact OAuth resource, and thereadscope.Integrations.tsxcontinues to render directly fromMCP_INTEGRATIONS; this adds no new list, section, or special UI.Why this change was made
Buildkite's public OAuth metadata confirms dynamic client registration and PKCE. Its hosted read-only endpoint provides a safer built-in default without inventing a tool-name allowlist.
Impact
Operators can connect Buildkite once from Settings > Integrations, and pasted or unfurled organization links now give Slack tasks an explicit setup recommendation when the built-in integration is unavailable. URL parsing uses bounded punctuation handling rather than the regex flagged by CodeQL, with direct repeated-punctuation coverage. Focused URL-detection, Slack-context, attachment-unfurl, and event-normalization tests passed alongside full
check-types,lint:fast, andgit diff --check. Live OAuth consent, tool discovery, and credential-backed Buildkite calls were not performed.Related PRs