Draft PRs and GitHub

Every change arrives as a draft pull request you review. Zaprex never pushes to your default branch or a protected branch.

Connect GitHub

Choose Connect GitHub in the Zaprex page. Ingot asks GitHub for repository access for Zaprex, then you add the repositories Zaprex may use. Disconnect anytime.

• Your GitHub token is stored encrypted and is only used by the Ingot server. It is never shown, logged, or passed into a sandbox.
• A dedicated Ingot GitHub App with least-privilege access per repository is coming later.

Branches

Zaprex creates a new branch named ingot-bot/<run>-<slug> from your default branch. It refuses to write to the default branch, main, master, protected branches and any branch that isn't its own, and it never updates an existing branch.

The pull request

Opened as a draft, with a summary, the files changed, the test result and a link to the run. Merging is always your call. There is a cap on open Zaprex PRs per repository so it never floods your queue.

Follow up on review comments

Leave comments on the draft PR and ask Zaprex to address them. It starts a follow-up run on the same repository.

Test mode

Until GitHub is connected, the portal shows Test mode: runs use a scratch workspace and no real pull requests are opened.