Repository navigation
Conversation
The us-west-1 runners run in Los Angeles, in Southern California. Claude-Session: https://claude.ai/code/session_012Z3Bufh7LxqRrqL85dhdiD
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
hlenke
left a comment
There was a problem hiding this comment.
Needs changes · Nothing to edit in the docs: the rename is complete and matches the product change, but hold the merge until checkly/monorepo#7027 ships, because today the product still says "N. California".
Merge gate. checkly/monorepo#7027 ("rename us-west-1 label from N. California to S. California") is OPEN; its description says it waits for product sign-off. On monorepo main (05df6b0ac7) the backend location defaults, the webapp location picker and the webhook sample event still name us-west-1 "N. California", so RUN_LOCATION and the UI would disagree with these pages if they merged today. The PR description already says to merge after the product change; I'm repeating it so the verdict is clear.
Completeness. At the PR head, git grep -i california finds no other "N. California" or "North California" in any .mdx, .json or .ts file, so every text mention is covered. #7027 uses the short form "S. California", which matches the construct comments and the RUN_LOCATION example; the plan sentence and the locations table use the long form "South California", parallel to "North Virginia" next to it. One binary image, images/learn/images/modern-rca-03.png, contains the string "California"; I could not check whether it shows the old name.
CI. preview-checks fails with 1 failed, 4 passed, 5 total without naming the check, the same failure as on other open PRs today (#859, #847); #860 should clear it. Not caused by this PR. All other checks pass.
Conflicts and overlap. MERGEABLE; main has not touched any of the six files since the merge base c6fb6612. #847 also edits the event-variable table in integrations/alerts/webhooks.mdx, but other rows, so either can land first. Draft #830 and #774 touch concepts/locations.mdx on other lines.
No inline comments.
What I checked
- Full diff from merge base
c6fb6612: 6 files, 7 one-line changes, all read. git grep -n -i californiaover the whole PR head, and forN. California/North Californiaacross.mdx,.json,.ts,.md: no leftovers.- Monorepo
mainat05df6b0ac7:apps/backend/api/src/models/defaults/locations.ts,apps/webapp/src/constants/locations.tsand the webhook channel sample still use "N. California". - checkly/monorepo#7027 (
gh pr view):OPEN, headbc25989c, changes those display names to "S. California", and lists this PR as its docs companion. gh pr checks 857, failed run 44523826020 log;gh pr view 857(MERGEABLE);git log <base>..origin/mainon the six files (no changes);gh pr listfor overlap;scripts/pr_impact.py(only hub-page info, no findings).- No end-to-end test: the local app runs monorepo
main, which still has the old name.
Rename the display name of us-west-1 from "N. California" / "North California" to "S. California" / "South California".
Why: our us-west-1 runners run in Leaseweb's Los Angeles data centre, which is in Southern California. The region code
us-west-1does not change.Matching product change: checkly/monorepo (linked below once open). Merge this after the product change ships, so the docs match the UI and the
RUN_LOCATIONwebhook value.Changed:
concepts/locations.mdx: plan text and locations tableconstructs/*.mdx: code comments next tous-west-1integrations/alerts/webhooks.mdx:RUN_LOCATIONexamplehttps://claude.ai/code/session_012Z3Bufh7LxqRrqL85dhdiD