Skip to content

docs: add the Drifted badge and the review before Sync to code (product update 2026-10-28) #748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hlenke wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add the Drifted badge and the review before Sync to code (product update 2026-10-28) #748

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions cli/monitoring-pull-requests.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.

Expand Down
Loading