ZynplexZPX Forgeby Zynplex
Platform.md

GitHub

ZPX Forge connects to GitHub through a GitHub App that each company installs on its account or organization, choosing which repos it can see.

Verified installation

When you come back from GitHub, the installation is only linked if:

  1. that same person started it, for that company;
  2. they are a company admin in ZPX Forge;
  3. they control the GitHub account: it is their own, or they are an admin of the organization.

An installation belongs to a single company.

Permissions the app requests

PermissionWhy
Contents · read and writeRead specs/; propose specs through pull requests
Pull requests · read and writeTrack and open PRs
Checks and statuses · read and writeRead or publish checks according to configuration
Deployments · writeApprove or reject the commit for a production environment protected by Forge Pro
Actions · readSee CI runs
Administration · read and writeProtect main and develop (optional)
Members · readMatch organization members

Branch protection

From a project, Protect develop and main creates a ruleset named ZPX Forge · ramas protegidas in the repo: changes only through pull requests, no deletion and no force-push. If it already exists, it is updated.

Webhooks and activity

Every delivery is verified with its signature (X-Hub-Signature-256), stored only once even if GitHub retries it, and processed in the background. It becomes project activity:

GitHub eventActivity
pushpush (flags whether specs/ changed)
pull_requestpr.opened, pr.merged, pr.closed, pr.reopened
failed check_suitecheck.failed
failed workflow_runci.failed
installation, installation_repositoriesSyncs installations and repos