#041Tutorial1 min

Prepare a fix from a finding

Request a fix proposal for an eligible finding in a connected repository.

Hackaiz team · updated 18/11/2026

Illustration: two developers review a change before approving it.
Illustration: two developers review a change before approving it. Illustrative photo, not a screenshot.

01When a fix can be prepared

A fix can be prepared for an eligible finding from a connected GitHub repository whose access is still valid. A website-only analysis gives no access to code: in that case Hackaiz explains what to change but cannot prepare a change.

02Steps

Preparation is a paid action; the actual total then appears in your statement.

  1. 1Open the finding from the report or the findings list.
  2. 2Click Prepare a fix.
  3. 3Hackaiz pins the exact repository version used for preparation.
  4. 4The proposal appears in Fixes with the status “ready for review”.

03What the proposal contains

Changed files and the line-by-line diff, the reason for the change, validations performed and known limits. It is stored server-side; nothing is sent to GitHub yet.

04What comes next

The proposal must be reviewed and explicitly approved by a person. Only after that approval is a change proposed on GitHub, on a dedicated branch, and Hackaiz never merges it.

Tip: Prepare fixes for Danger findings first: they reduce risk the most.

Frequently asked questions

Take the next step

Was this article helpful?

Related articles