Installations

Installations determine which GitHub repositories Mogplex can see and which repos are eligible for app-backed automation features.

There is not a separate top-level app route called /installations today. This docs page describes the GitHub App installation state surfaced through Settings and consumed by Projects, Triggers, and Automations.

What an installation unlocks

• Import repositories into the default project
• Keep repository metadata in sync with GitHub
• Mark repos as eligible for trigger- and automation-driven work
• Attach GitHub-backed automation coverage to the right repos

Important distinction

GitHub OAuth can be enough to connect an account and discover repositories, but GitHub App coverage is what unlocks trigger-backed automation and related repo actions.

What the app shows

Inside Settings, each installation shows:

• the account or org it belongs to
• the installation scope
• how many repos GitHub reports under that installation
• how many repos Mogplex has already synced
• a direct manage link back to GitHub when metadata is available
• the synced repos Mogplex currently associates with that installation

If a repo appears in Projects but is still not triggerable, the usual cause is missing App coverage for that owner.

If cached installation state is missing, Mogplex can also reconcile the user's GitHub installations again and hydrate the metadata from GitHub before rendering the Settings view.

Where this shows up in the app

• Projects shows the imported repos and workspaces
• Automations uses installation-backed repos for GitHub events
• Settings is where account connections and related setup live
• Triggers only offers installations that are actually available for webhook-backed routing