Skip to main content
GitHub is Platinur’s version-control and promotion backbone. Generated dbt models and Evidence code are committed to a configured repository. A named release reconstructs a dependency-closed selection on a fixed branch from current Production and opens a pull request; independent Staging changes can remain unreleased and are replayed after merge. Install the Platinur GitHub App on your organization or repository. You do not provide or manage a personal GitHub token; Platinur mints short-lived installation tokens when it needs them.

​
Repository is optional up front

You do not need to configure a repository during setup. If the GitHub App is installed on an organization and no repository is configured yet, Platinur automatically creates a private managed repository (named platinur-<company-slug>) the first time a GitHub-requiring action runs — applying a change to Staging, or Publish. If the App is installed on a personal/user account, or no App is installed, that first action fails with a message telling you to connect GitHub here or move the installation to an organization.

​
Install the GitHub App

  1. Open Configuration in the portal.
  2. Click Install on GitHub. If the button is unavailable, contact Platinur Support.
  3. GitHub opens the App installation page. Select the repository that holds the Platinur project and confirm.
  4. GitHub redirects back to the portal automatically.
  5. The portal shows a GitHub App connected confirmation. Platinur stores the installation_id for the account and no personal token is needed from this point on.

​
How it works

Platinur mints short-lived installation access tokens scoped to your account’s installation whenever it needs to interact with GitHub — pushing commits, opening PRs, reading branches. Tokens are cached in-process and refreshed automatically near expiry; you never handle or store them. Per-account state is limited to the installation_id, a non-secret numeric identifier issued by GitHub at install time.

​
Security notes

  • Per-account state is limited to the non-secret GitHub App installation_id.
  • Installation tokens are minted on demand, cached briefly, and never persisted to disk.
  • Generated dbt and Evidence code committed to your repository is the only code Platinur writes there — Platinur never pushes to branches outside the configured staging/production pair.

​
Advanced settings

Under the GitHub card’s Advanced disclosure: