GitHub App Coverage

Understand the difference between GitHub sign-in and GitHub App coverage, and verify why a repo is or is not triggerable.

Most confusion in Mogplex setup comes from mixing up two different GitHub states:

  • GitHub connected through GitHub sign-in
  • GitHub App installed for the account or org that owns the repo, with the installation linked to you

They are related, but they do different jobs.

Sign-in vs App coverage

The GitHub connection (GitHub OAuth) gives Mogplex your GitHub identity and your org memberships. It does not grant repository access. Signing in to Mogplex with GitHub is a separate step that only identifies you.

GitHub App coverage determines which repos Mogplex can access, and which it can treat as triggerable for webhook-backed work such as Triggers and Automations. Coverage comes from an installation linked to you: on your personal account, or on an org where you are an org owner. Org members who are not owners use team-shared repositories instead. See Who can link an installation.

Common symptoms of missing App coverage

  • Triggers is empty even though GitHub is connected
  • Automations cannot find the installation or repo you expect
  • An org you belong to is missing from Settings
  • Settings shows GitHub connected, but installation coverage is missing or for the wrong owner

How to verify coverage

Start in Settings.

Check the GitHub App coverage and installation area. You want to verify:

  • the installation belongs to the correct account or org
  • the repo count and synced repo count look reasonable
  • the repo owner you care about appears under an installation

If installation metadata is available, use the manage link back to GitHub to confirm the App is installed where you think it is.

What to do next

If GitHub is connected but no installation is linked to you for the repo owner:

  1. Install or configure the Mogplex GitHub App for that owner. For an org, an org owner must do this. See An org you belong to does not appear.
  2. Return to Settings and refresh the installation state
  3. Go back to Projects and sync repos again
  4. Re-check Triggers or Automations

Rule of thumb

If the question is "why can't Mogplex use this repo or route webhook work for it?", the answer is usually an installation that is not linked to you, not GitHub sign-in.

Edit on GitHub

On this page