Skip to content

GitHub App and Repo Pull Requests

On every plan, you can deliver approved fixes as GitHub pull requests instead of - or in addition to - applying them live on the site through the connector (Repo Pull Requests).

This uses a Patcherly GitHub App you install on your organisation or repositories. It is not the same as Sign in with Google or GitHub (that flow only identifies your dashboard account and never reads or writes repositories).

Install the App (once per workspace)

  1. Open Profile → Account.
  2. On the Connected repositories card, choose Connect GitHub App (you need the Manage Repo Pull Requests workspace permission).
  3. Complete the GitHub install screen for the org or repos you want Patcherly to use.
  4. When GitHub redirects back, the card shows the connected account.

One GitHub App installation binds to one Patcherly workspace. The same GitHub install cannot be claimed by two workspaces.

Disconnecting the App from Profile resets every site in that workspace to Live Patch and clears linked repo fields.

Still on Profile → Account → Connected repositories, for each site:

  1. Choose Link repository, then pick a repo and base branch from the dropdowns (no free-text).
  2. Optionally set a path prefix.
  3. Choose a delivery mode (Live Patch, PR Only, or Live Patch + Repo PR). Modes that open a PR are available only after the site is linked, and not while Dry-run is on.

From Sites, More actions → Link repository (or Manage repository when a repo is already linked) opens this same Profile card for that site. A red pen appears only when the site uses PR Only or Live Patch + Repo PR and App/repo/branch setup is still incomplete. The expanded row shows Patch Method for the current mode.

Mode What happens after Approve
Live Patch (default) The connector applies the fix on your server (same as before).
PR Only Patcherly opens a PR on the linked repo. The Errors list shows Awaiting PR merge until the PR is merged or closed.
Live Patch + Repo PR Patcherly opens a PR, then also applies live via the connector. The live apply result drives success or failure; the PR is informational.

Awaiting PR merge

When a site is PR Only and you approve a fix, Patcherly:

  1. Opens a branch patcherly/{error_id} and a pull request against your base branch.
  2. Shows status Awaiting PR merge (with a link to the PR when available).
  3. When the PR is merged, marks the error fixed.
  4. When the PR is closed without merge, marks the error failed so you can retry or mark it fixed manually.

Merge completion uses the GitHub App webhook. If the webhook is misconfigured, a row can stay on Awaiting PR merge — use Mark Fixed as the escape hatch (that may leave an open PR on GitHub; a later webhook update only refreshes PR metadata).