Skip to main content

​
Overview

Patching turns a finding into a proposed pull request against the repository and branch you select, giving engineers a concrete change to review and validate.

​
Patching Use Cases

Use patching when you want MindFort to turn finding context into a proposed code change. Patching is best for platform-generated pull requests. If your team wants to use a local AI copilot inside its own checkout, connect the copilot through MCP so it can read MindFort finding evidence and remediation advice from the platform.

​
Prerequisites

​
Create a Patch

  1. Open a finding from the Findings view.
  2. Select Patch in the finding actions.
  3. Select a linked repository.
  4. Select the base branch the PR should target.
  5. Click Create PR.
MindFort will begin generating the patch. While the patch is being created, the button shows a “Patching” status indicator. Once complete, a View PR link appears so you can review the changes on GitHub.

​
Review and Merge

After the PR is created:
  1. Review the proposed changes on GitHub.
  2. Run your CI/CD checks as usual.
  3. Merge when satisfied.
  1. Start with high- and critical-severity findings.
  2. Always review the generated PR before merging — treat it as a starting point.
  3. Deploy the reviewed changes, then re-run an assessment or retest to check whether the reported issue still reproduces.

​
Patch status and finding status

Patch status tracks the generated pull request. A merged patch does not, by itself, prove that a deployed vulnerability is fixed or mark the finding resolved. When the organization has automatic retesting after patch merge configured, the finding shows the queued or scheduled validation and its result. See Automatic retest status.