Skip to main content

​
Overview

Patching lets you generate a pull request that addresses a finding, directly from MindFort. The platform analyzes the finding, writes a fix, and opens a PR against the repository and branch you select.

​
Patching Use Cases

Use patching when you want MindFort to turn finding context into a proposed code change.
Use CaseHow It Helps
Fix a confirmed findingGenerate a PR from the finding’s evidence, impact, and remediation advice.
Speed up remediation reviewGive engineers a concrete patch to inspect instead of starting from a blank ticket.
Handle repeated bug classesPatch similar access-control, validation, or configuration issues faster after a pattern is understood.
Prepare for retestMerge a reviewed fix, then re-run an assessment or targeted task to validate the result.
Connect security and engineering workflowsKeep the finding linked to the generated PR so teams can move from evidence to code review.
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

  • A GitHub integration must be connected. Go to Settings > Integrations to set up the connection.

​
Create a Patch

  1. Open a finding from the Findings view.
  2. Click the Create Patch button in the finding actions bar.
  3. Select the repository that corresponds to the target.
  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. Re-run an assessment or retest after merging to confirm the finding is resolved.