Check Deployment Status

Check whether a PR/commit is deployed to staging and production using the continuous-deployment MCP tools.

Usage

CODEBLOCK0

Key Concepts

PR Head Commit != Merge Commit

When a PR is merged via SubmitQueue, the merge commit on main is DIFFERENT from the PR's head commit. The continuous-deployment system tracks the merge commit, not the PR head.

Workflow:

1. 1. Get PR metadata → extract head SHA
2. Use findServiceCommits with search text to find the actual merge commit on main
3. Use getCommitDeploymentStatus with the merge commit hash

UP Deployment Stages

Stage	Meaning
Build created	Binary built from commit
Deployed to staging

Running on staging instances | | Soaked | Staging soak period passed | | Waited for deployment window | Outside deploy freeze windows | | Introduced to production | Fully deployed to production — code is live |

"Introduced to production" = fully deployed. Not partial, not in-progress. The commit is running on all production instances.

Deployment Status Values

Status	Meaning
INLINECODE2	Commit is running in this environment
INLINECODE3

Deployment in progress | | (empty) | Not deployed to this environment |

Step-by-Step Workflow

Step 1: Get PR Metadata

Use mcp__code-mcp__get_github_pull_request_metadata:
CODEBLOCK1

Extract: title, head SHA, merged status, base branch.

Step 2: Find Merge Commit

The PR head SHA won't be found in deployment system. Search for the merge commit:

Use mcp__continuous-deployment__continuousdeployment_findservicecommits:
CODEBLOCK2

The result includes the merge commit hash, serial number, and code review metadata linking back to the PR.

Step 3: Check Deployment Status

Use mcp__continuous-deployment__continuousdeployment_getcommitdeploymentstatus:
CODEBLOCK3

Returns deployment status per service per environment (staging, production, bits-test-sandbox).

MCP Tools Reference

continuous-deployment MCP

Tool	Purpose
INLINECODE7	Search commits by service name, author, text, date range
INLINECODE8

Get deployment status of a commit across all environments | | listServiceCommits | List recent commits for a service (with serial-based pagination) | | getCommitsInDeployment | List commits in a specific deployment task | | listCommitSegments | Get deployment segments for a service | | getConfigForService | Get continuous deployment config for a service |

code-mcp

Tool	Purpose
INLINECODE13	PR status, author, labels, SubmitQueue status
INLINECODE14

PR diff content | | get_github_pull_request_comments | PR comments |

UCS deployer MCP

Tool	Purpose
INLINECODE16	Rollout status for a specific deployment object
INLINECODE17

Read deploy state |

Service-Name Only Mode

If only a service name is provided (no PR/commit):

Use mcp__continuous-deployment__continuousdeployment_listservicecommits:
CODEBLOCK4

Then check deployment status for each returned commit using Step 3.

Common Patterns

Stacked PRs

For stacked PRs, each PR may affect different services. Check deployment per-service:

• - PRs changing marketing-recommendations/ → check marketing-recommendations service
• PRs changing ads-insights/ → check ads-insights service

Repository URI

For go-code monorepo, always use: INLINECODE23