From 55b036b5c6ffbede021797247192e756705ad7e9 Mon Sep 17 00:00:00 2001 From: Hannes Lenke Date: Wed, 28 Oct 2026 21:26:40 -0400 Subject: [PATCH] docs: add the Drifted badge and the change review before Sync to code (webapp 2026-10-28) A code-managed resource changed in Checkly after its last deploy shows a Drifted badge next to Managed by. Clicking it opens the Export to code dialog's Code tab, which lists what changed since the deploy with the old and new value of each property, and lists changes the sync can't write yet under "Changed in Checkly, but kept as it is in code". The page did not mention the badge or the review. Proven on the local webapp and API at monorepo commit 5858d7e03f with a project deployed by checkly 10.0.0 (checkly/monorepo#4776). Co-Authored-By: Claude Opus 5.5 --- cli/monitoring-pull-requests.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/cli/monitoring-pull-requests.mdx b/cli/monitoring-pull-requests.mdx index 4dc16b82..8fe93f47 100644 --- a/cli/monitoring-pull-requests.mdx +++ b/cli/monitoring-pull-requests.mdx @@ -18,7 +18,7 @@ Review monitoring changes in GitHub, test them, and deploy the merged code to Ch ## 1. Connect GitHub and choose a repository -Open the resource's **Export to code** dialog and select **Code**. If prompted, authorize GitHub from Checkly, choose an installation you own, and click **Connect**. Grant the App access to your repository. See [GitHub integration setup](/integrations/ci-cd/github/deployments#set-up-github-deployment-hooks) for installation help; you don't need a deployment hook for this workflow. +Open the resource's **Export to code** dialog and select **Code**. A code-managed resource that was changed in Checkly since its last deploy shows a **Drifted** badge next to **Managed by** on its page; clicking the badge opens the same **Code** tab. If prompted, authorize GitHub from Checkly, choose an installation you own, and click **Connect**. Grant the App access to your repository. See [GitHub integration setup](/integrations/ci-cd/github/deployments#set-up-github-deployment-hooks) for installation help; you don't need a deployment hook for this workflow. For a UI-created resource, choose the repository to export into. If it has multiple Checkly configs, select the folder for your project. Checkly can add the resource to a project already deployed to this account or create a config for a new project. @@ -27,7 +27,7 @@ For a code-managed resource, Checkly uses its project's repository. If asked, ch ## 2. Open the PR - **UI-created resource:** click **Export to code**. Checkly generates the code and temporarily reserves the existing resource for the project. Your monitoring keeps running; ownership stays pending until you deploy. -- **Code-managed resource:** save your UI changes, then click **Sync to code** to send them to its source file. **Already in Sync** means there's nothing to send. +- **Code-managed resource:** save your UI changes. The **Code** tab lists what changed in Checkly since the last deploy, with the old and new value of each property. Changes the sync doesn't write are listed under **Changed in Checkly, but kept as it is in code**. Click **Sync to code** to send the changes to its source file. **Already in Sync** means there's nothing to send. Open the PR from the dialog or your project's **Pull requests** view in **Projects**. That view tracks PRs created through Checkly, with **Open**, **Merged**, and **Closed** filters.