Applying fixes & pull requests

Reviewing recommendations is only half of Obics; the other half is applying them. When you approve a suggestion, Obics writes the code change and opens a pull request against your own repository. This page walks the full lifecycle.

Creating a pull request

Open a recommendation (from logs or metrics) and find its suggestion cards. Each card has a primary button:

• Create PR (or “Create Merge Request” on GitLab): the normal case. Clicking it immediately queues the fix; there’s no branch or repo picker at this point because those are configured ahead of time (see below).
• Prepare Fix: shown instead when the suggestion has side effects (a vendor-side change). Prepare the fix first, then reopen the recommendation to review and apply those side effects.

You can also skip the popup entirely: a row’s ⋮ → Quick Fix applies the top-ranked suggestion directly from the list.

Where PR options come from

Target branch, branch naming, commit prefix, required reviewers and work-item creation are all set once under Settings → Pull Requests (see Settings) and per-repo in the repository picker, not at click time.

What Obics does after you click

Behind the scenes Obics:

1. Marks the recommendation Queued, then Running.
2. Clones your connected repository at the relevant commit.
3. Uses an AI agent to generate the code fix (in a multi-repo org it may change several repos and open a PR for each).
4. Creates a branch, commits, and pushes, using your configured branch-name template and commit-message prefix.
5. Opens the pull/merge request against your target branch, optionally adding required reviewers and creating a linked work item.
6. Updates the status to PR Created (a link) or Failed (hover shows why). If you enabled it, you get an email with the PR link or the failure reason.

Tracking status

Each recommendation shows a status badge:

Badge	Meaning
Queued	Waiting to run.
Running	The fix is being generated.
PR Created	The PR is open; the badge links to it. It also moves to the Fix Ready tab.
Failed	The fix couldn’t be produced; see the Fix Failed tab.
Resolved	The fix landed and is done, in the Resolved tab.

An amber “action needed” icon on a PR Created item means the PR alone didn’t finish the job: there are manual steps or vendor-side actions still to apply.

The Fix Result panel

Once a fix exists, opening the recommendation shows a Fix Result panel:

• What the fix did: a description of the change.
• Action required: any manual steps, with an “I’ve completed these manual steps” checkbox.
• Side-effect cards: Exclusion Filters to apply, Metrics to generate from logs, Metric tags to configure. Each has an Apply button (→ Applying… → Applied, with Reapply), an “I’ve done this manually” checkbox, and step-by-step vendor instructions.
• Footer buttons: Resolve, Open PR (a dropdown per repo for multi-repo fixes), and Delete Fix.

Side effects aren’t automatic

Code changes go into the PR, but vendor-side changes (like a Datadog exclusion filter) are not applied for you; you apply them from the Fix Result panel or do them manually and tick the checkbox.

When the PR merges

When Obics detects your PR was merged it shows a “PR merged” banner and, unless manual steps remain, the fix resolves automatically, or you click Resolve to move it to the Resolved tab yourself. The realized savings then count toward the Resolved savings badge and the Cost Explorer.

Delete Fix only removes the item from Obics; it does not delete the branch or PR in your provider.