GitHub integration

Proposed PRs, not autonomous merges

Read repository and branch context, open pull requests with a proposed patch and present a reviewable diff with evidence — while merging and deploying stay with your team. AI proposes; humans approve.

Book a demo See remediation

Proposed PRs onlyHumans merge & deployCapability-level health

What it does

Context, a proposed change, a reviewable diff

Repository & branch context

Read repository and branch context so a proposed change is grounded in the real codebase — scoped to the bound project and tenant.

Proposed pull requests

Open a pull request carrying a proposed patch, where the GitHub App is installed with the right permissions. FixControl proposes; it does not merge.

Diff & evidence

The proposed change arrives as a reviewable diff with the evidence behind it, so an engineer reviews a real PR, not an opaque action.

Human merge & deploy

Merging and deploying stay with your team. AI never merges or ships to production on its own — those are human approvals.

Scoped permissions

Actions run under the installed GitHub App’s permissions, so FixControl can only do what your installation explicitly allows.

Evidence & audit

Opening a PR is a recorded, attributable action, so the repository history and the decision ledger agree.

Capabilities & health

Capability-level status, not one green checkmark

GitHub may be connected for repo read while the PR-open path depends on the app install and permissions. FixControl shows each capability’s health honestly.

Read repo & branch context

Supported

FixControl reads repository and branch context within the bound project and tenant to ground a proposed change in the real codebase.

Open PR with proposed patch

Configuration-dependent

Requires the GitHub App to be installed with the right permissions on the target repository. Outbound writes route through the outbox with retry and dead-letter handling.

Diff & evidence on the PR

Supported

The proposed change is presented as a reviewable diff with its supporting evidence, so an engineer reviews a real pull request.

Merge or deploy autonomously

Not available — by design

FixControl proposes PRs; it does not merge or deploy to production on its own. Merging and shipping are human approvals, by design.

Single green ‘connected’ status

Not available — by design

By design. GitHub may be connected for repo read while the PR-open path is unavailable. FixControl surfaces capability-level health instead of a single green checkmark.

How failures are handled

No autonomous merge or deploy

Outbox, retry and audit

Opening a pull request routes through the integration outbox with retry and dead-letter handling, and failures surface in the operational timeline. FixControl proposes the change; a person reviews the diff and merges. The decision is written to the decision ledger with actor, role, channel, evidence and consequence.

FAQ

Common questions

Does FixControl merge pull requests or deploy on its own?+

No. FixControl proposes a pull request carrying a patch; merging and deploying stay with your team. AI never merges or ships to production autonomously — those are human approvals.

What does FixControl need to open a PR?+

The GitHub App must be installed on the target repository with the permissions to open pull requests. Without that, repo read may still work while the PR-open capability is unavailable.

How does an engineer review a proposed change?+

As a real pull request — a reviewable diff with the evidence behind it. There is no opaque action; the change is visible in the PR and in the timeline.

What happens if opening a PR fails?+

The write routes through the integration outbox with retry and dead-letter handling, and the failure is visible in the timeline rather than silently dropped.

Are GitHub actions audited?+

Yes. Opening a PR is written to the decision ledger with the actor, role, channel, evidence shown and the consequence, so the repository history and the ledger agree.

Keep exploring

Support → engineering

Turn a support ticket into a governed, reviewable engineering PR.

GitLab

The same governed remediation flow with merge requests.

Deployment governance

Keep merge and deploy as human-approved steps after the PR.

Bring governed AI to GitHub

See repository context, proposed PRs and diff evidence run under governance — with merge and deploy staying human — on a live demo.

Book a demo Ask FixControl