FixControl
GitLab integration

Proposed MRs, not autonomous merges

Read repository and branch context, open merge 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 demoSee remediation
Proposed MRs 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 merge requests

Open a merge request carrying a proposed patch, where the GitLab connection has 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 MR, 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 configured GitLab connection’s permissions, so FixControl can only do what your setup explicitly allows.

Evidence & audit

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

Capabilities & health

Capability-level status, not one green checkmark

GitLab may be connected for repo read while the MR-open path depends on the connection’s 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 MR with proposed patch
Configuration-dependent

Requires the GitLab connection to have the right permissions on the target project. Outbound writes route through the outbox with retry and dead-letter handling.

Diff & evidence on the MR
Supported

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

Merge or deploy autonomously
Not available — by design

FixControl proposes MRs; 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. GitLab may be connected for repo read while the MR-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 merge 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 merge requests or deploy on its own?+
No. FixControl proposes a merge 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 an MR?+
The GitLab connection must have permissions to open merge requests on the target project. Without that, repo read may still work while the MR-open capability is unavailable.
How does an engineer review a proposed change?+
As a real merge request — a reviewable diff with the evidence behind it. There is no opaque action; the change is visible in the MR and in the timeline.
What happens if opening an MR 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 GitLab actions audited?+
Yes. Opening an MR 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 MR.

GitHub

The same governed remediation flow with pull requests.

Deployment governance

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

Bring governed AI to GitLab

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

Book a demoAsk FixControl