Table of contents

GitHub deployments

GitHub deployments are webhook events triggered by GitHub whenever a deployment service reports a successful deployment event. This works out-of-the-box with the following services.

• Vercel for GitHub
• Heroku Pipelines

Any (SaaS) service that interacts with the GitHub deployments API and reports the correct “success” message will work, both with production and preview deployments.

1. Go to the integrations tab in your account settings and click the “Integrate with GitHub” button.
   

2. You will be redirected to GitHub and prompted to select an account and install the Checkly GitHub App.
   

3. When accepting the installation, you are redirected back to Checkly and the integration is installed. Now, go to the CI/CD tab of the check you want to link to a GitHub repository. In Browser checks, this will be under “Change settings”.

4. Click the “Link GitHub repo” button and select the repository you want to link.
   

5. On each deployment event, we will run your check and report the results directly in your GitHub timeline and PR overview.
   

6. You will also get an overview of the check result in the details section

GitHub reports an environment URL on each deployment event. Depending on what deployment service you use, this environment URL can be used to run your check on different target environments than configured in your check.

The primary use case for this is validating temporary review/branch deployments, such as those provided by Vercel and Heroku Pipelines, before going to production.

So, when you enable the “Use environment URL from deployment trigger” checkbox there are two scenarios:

With API checks, we replace the hostname part of your request url with the host in the environment URL. For example:

• Your configured URL: https://api.acme.com/v1/customers?page=1
• Environment URL: https://now.customer-api.qis6va2z7.now.sh
• Replaced URL: https://now.customer-api.qis6va2z7.now.sh/v1/customers?page=1

Notice we only replace the host part, not the URL path or any query parameters.

For browser checks, the environment URL is exposed as the ENVIRONMENT_URL environment variable. This means you can use that variable in your code to replace any hardcoded URL you might have, i.e.:

import { expect, test } from '@playwright/test'

test('assert response status of page', async ({ page }) => {
  const targetUrl = process.env.ENVIRONMENT_URL || 'https://www.checklyhq.com'
  const response = await page.goto(targetUrl)

  expect(response.status()).toBeLessThan(400)
})

const { expect, test } = require('@playwright/test')

test('assert response status of page', async ({ page }) => {
  const targetUrl = process.env.ENVIRONMENT_URL || 'https://www.checklyhq.com'
  const response = await page.goto(targetUrl)

  expect(response.status()).toBeLessThan(400)
})

This way we are setting the targetUrl variable to either the ENVIRONMENT_URL or just our main production URL.

Whenever a Preview deploy happens on GitHub, this check gets called and runs the script against the preview environment. This check also runs on a set interval, and checks our production environment.

This way, we kill two birds with one stone and don’t need separate checks for separate environments.

How to Integrate Vercel with Checkly? Step-by-Step Guide Command Line triggers

Last updated on August 16, 2024. You can contribute to this documentation by editing this page on Github