Skip to main content

GitHub Integration

Open in QuickMonitoring→ Sites → [Your Site] → Settings → GitHub

Connect your GitHub repository to a site and QuickMonitoring will automatically trigger a scan on every push. No manual intervention required — every deployment gets checked.

What you'll see​

Once connected, the GitHub section in Site Settings shows:

  • The connected repository name and branch filter (if set)
  • The last webhook event received and its result (scan triggered / skipped)
  • A button to disconnect or change the linked repository

How to set up​

Step 1: Connect your GitHub account​

  1. Go to Organization Settings → Integrations
  2. Click Connect GitHub
  3. Complete the GitHub OAuth flow — you will be redirected back to QuickMonitoring automatically
  4. Your GitHub account is now linked to your organization
  1. Go to Sites → your site → Settings → GitHub
  2. Select the repository from the dropdown (only repositories you have access to appear)
  3. Optionally enter a branch filter — only pushes to that branch will trigger scans (e.g. main or production)
  4. Click Save

QuickMonitoring automatically installs a webhook on the selected GitHub repository. You do not need to configure anything on the GitHub side.

Scan tier by push size​

QuickMonitoring selects the scan depth automatically based on how many files changed in the push:

Files changedScan mode
1 – 5 filesQuick scan
6 – 20 filesStandard scan
21+ filesFull scan

This keeps feedback fast for small fixes while ensuring comprehensive coverage for large deploys.

Skipping a scan​

Add one of the following flags to your commit message to prevent a scan from being triggered:

  • [skip-scan]
  • [no-scan]
  • [skip-qa]

Example:

git commit -m "fix typo in README [skip-scan]"

Scans are also automatically skipped when:

  • The push only modifies documentation files (.md, .txt, .rst)
  • A scan for the same site is already running (10-minute cooldown applies between scans)

Regression email​

If a scan triggered by a push finds new issues that were not present in the previous scan, QuickMonitoring sends a regression email to all organization members. The email includes:

  • Which push triggered the scan (commit SHA and author)
  • The categories where new issues appeared
  • A direct link to the Quality Report for that scan

This makes it easy to catch regressions at the commit level rather than discovering them in production.

Pass condition​

✅ You've earned this achievement when a GitHub repository is linked to a site and at least one scan has been triggered automatically by a push.

Common issues​

  • Repository not appearing in the dropdown — Make sure you granted QuickMonitoring access to the repository during the OAuth flow. Go to Organization Settings → Integrations → Manage GitHub permissions to update access.

  • Webhook events not arriving — Check the webhook status in your GitHub repository under Settings → Webhooks. If it shows delivery failures, disconnect and reconnect the integration from Site Settings to reinstall the webhook.

  • Scans triggered on the wrong branch — Set a branch filter in Site Settings to restrict scans to a specific branch. Without a filter, any push to any branch triggers a scan.

  • Scan not triggered after a push — If a scan was already running within the last 10 minutes, the new push is skipped due to the cooldown. The skipped event is logged in the GitHub section of Site Settings.

  • Docs-only push should have been skipped but wasn't — The docs-only skip applies when all changed files match documentation file extensions. If your repo stores documentation alongside source files (e.g. docs/ inside a mixed repo), some pushes may not qualify for the skip.