Re-running a Scan
How to run a new scan after fixing findings to verify your progress.
After fixing issues, run a new scan to see what's been resolved.
Step 1: Push your fixes to GitHub
Commit your changes and push to the branch you connected to FinishKit:
git add .
git commit -m "fix: address FinishKit findings"
git pushStep 2: Start a new run
Go to your project page and click Run Scan again.
FinishKit always scans the latest commit on your connected branch, so it will automatically pick up your changes.
Step 3: Compare results
When the new run completes, your Finish Plan will reflect the current state of your code. Findings that you've resolved will no longer appear.
Each scan is a fresh analysis. FinishKit doesn't "remember" that a finding was previously there. If you fix something and the finding disappears in the next scan, it's resolved.
Step 4: Repeat until you're happy
Keep fixing and re-scanning until:
- All blockers and critical findings are resolved
- You're comfortable with the remaining medium/low findings
- You feel confident shipping
How many scans do I need?
There's no magic number. Most users do 2-4 rounds of scan, fix, and re-scan before they feel ready to ship. The first scan usually has the most findings; each subsequent scan has fewer.