From af0e2b66a76645d638886cccdffdd1048da0af50 Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:29:51 +0000 Subject: [PATCH 1/6] docs: add pentest retests and clarify scan limits Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- code-review/overview.mdx | 10 ++++ code-review/troubleshooting.mdx | 11 +++++ docs.json | 4 ++ white-box-pentest/billing.mdx | 10 ++++ white-box-pentest/overview.mdx | 6 +++ white-box-pentest/retests.mdx | 86 +++++++++++++++++++++++++++++++++ 6 files changed, 127 insertions(+) create mode 100644 white-box-pentest/retests.mdx diff --git a/code-review/overview.mdx b/code-review/overview.mdx index 94be089..5d0b7b5 100644 --- a/code-review/overview.mdx +++ b/code-review/overview.mdx @@ -7,6 +7,16 @@ Code Review reviews pull requests and merge requests in the repositories you ena Use Code Review for continuous security coverage on day-to-day development. For broader, scoped assessments of a repository or application, use [White-box Pentest](/white-box-pentest/overview). +## Scan limits + +Code Review scans pull requests and merge requests with **up to 500 changed +files**. Larger changes are skipped, not partially scanned. Split them into +separate PRs or MRs with no more than 500 changed files each. + +This per-scan limit is separate from your organization's +[pooled review allowance](/code-review/spillover-usage). Enabling spillover +does not raise the file limit. + ## Quickstart diff --git a/code-review/troubleshooting.mdx b/code-review/troubleshooting.mdx index 47adaa6..823c53c 100644 --- a/code-review/troubleshooting.mdx +++ b/code-review/troubleshooting.mdx @@ -13,6 +13,7 @@ Check these first: - The repository appears in **Repositories** - The repository is enabled for Code Review - The pull request or merge request targets a covered branch +- The pull request or merge request changes no more than 500 files - The organization has trial or paid review capacity available - The organization has not reached its pooled review limit, or spillover is enabled on a paid plan - For GitHub, the GitHub App installation includes the repository @@ -43,6 +44,16 @@ Check **Billing** to confirm the organization has trial or paid review capacity If auto-assigned seats are enabled and a new developer did not get assigned a seat, you may need to [increase the auto-assignment seat limit](/code-review/people#configure-the-seat-limit). +## Pull request or merge request is too large + +Each PR or MR scan supports **up to 500 changed files**. If a change exceeds +that limit, Hacktron skips the entire review. It does not scan the first 500 +files, and the skipped review does not count toward your pooled review allowance. + +Split the change into separate PRs or MRs with no more than 500 changed files +each. Splitting commits within the same PR or MR does not reduce its file +count. Enabling spillover does not bypass this limit. + ## Review limit is reached Code Review uses a pooled organization review limit each billing period. If the limit is reached: diff --git a/docs.json b/docs.json index 8182e5a..ad21c55 100644 --- a/docs.json +++ b/docs.json @@ -140,6 +140,10 @@ "group": "Getting started", "pages": ["white-box-pentest/quickstart"] }, + { + "group": "After the scan", + "pages": ["white-box-pentest/retests"] + }, { "group": "Credits and billing", "pages": ["white-box-pentest/billing"] diff --git a/white-box-pentest/billing.mdx b/white-box-pentest/billing.mdx index 62593de..d39c6b8 100644 --- a/white-box-pentest/billing.mdx +++ b/white-box-pentest/billing.mdx @@ -87,6 +87,16 @@ organization has insufficient Whitebox Scan credits. updated. +## Retests + +Each White-box Pentest includes **one free retest**, with no additional +Whitebox Scan credits deducted. You can request it only once per scan, so +finish all the fixes you want verified before submitting. + +For further verification, start a new scan or contact `hello@hacktron.ai`. +A new scan uses the usual Whitebox Scan credits. See +[Retests](/white-box-pentest/retests) for the request steps and results. + ## Refunds and cancellations If a started scan cannot launch successfully after credits are deducted, diff --git a/white-box-pentest/overview.mdx b/white-box-pentest/overview.mdx index ffd2fdc..43cda71 100644 --- a/white-box-pentest/overview.mdx +++ b/white-box-pentest/overview.mdx @@ -37,6 +37,12 @@ White-box Pentest is a good fit when you need: +## Verify your fixes + +Each scan includes **one free retest**. Once you have fixed the findings you +want verified, [request a retest](/white-box-pentest/retests) from the completed +scan. Hacktron verifies the fixes and makes an updated report available. + ## Run status | Status | Meaning | diff --git a/white-box-pentest/retests.mdx b/white-box-pentest/retests.mdx new file mode 100644 index 0000000..f5b9eac --- /dev/null +++ b/white-box-pentest/retests.mdx @@ -0,0 +1,86 @@ +--- +title: "Retests" +description: "Ask Hacktron to verify your fixes and download an updated pentest report. Each scan includes one free retest." +--- + +After you fix findings from a White-box Pentest, request a retest from the scan +page. The Hacktron team verifies the fixes and records the result for each +finding. + + + **Each scan includes one free retest.** You can request a retest only once per + scan, so finish all the fixes you want verified before submitting. You cannot + submit another request while the retest is pending or after it is completed. + + +## Before you request a retest + +- The scan must be **Completed**, with triage finished and at least one reported finding to retest. +- You need an organization role of **Member** or higher to submit a request. Viewers can read the results. +- Retests are available for White-box Pentests on the hosted platform, not Code Review scans or on-premises deployments. +- Have the branch or commits containing your fixes ready. If the fixes are deployed, have the deployment URLs ready too. + +A retest checks findings from the original scan. To assess new features or +expand the scope, [start a new pentest](/white-box-pentest/quickstart). + +## Request a retest + + + + Go to **Whitebox Scans**, open the scan, and click **Request retest**. + + + For each repository, choose the branch containing your fixes. You can also + add commit SHAs under **Commits**, pressing Enter after each one. + + Add **Deployment URLs** if the fixed version is running, and use + **Summary of fixes** to explain what changed and anything the team needs + to know when verifying. Both fields are optional. + + For a scan of uploaded code, you cannot select a replacement archive here. + Describe the changes in the summary. + + + + Check the findings included in the retest. Findings marked **False + positive** or **Accepted risk** are excluded. If a finding should be + excluded, update its status before submitting. + + + Review the repositories, deployment URLs, and summary in **Confirm**, + then click **Request retest**. The scan shows **Retest pending** while + Hacktron verifies the fixes. + + + +### Request limits + +- Up to **50 commit SHAs per repository**, each 7 to 40 hexadecimal characters +- Up to **20 deployment URLs**, each starting with `http://` or `https://` +- Up to **10,000 characters** in the summary of fixes + +## Read the results + +Open **Retest result** on the scan page to check progress. Once verification +is complete, the scan shows **Retested** and each included finding has an +outcome and verification notes: + +| Outcome | Meaning | +| ------------------ | ----------------------------------------------------------------- | +| **Verified fixed** | Hacktron verified the fix. Open findings are marked **Resolved**. | +| **Not fixed** | The issue remains. Read the notes for details. | + +If you have email notifications enabled, Hacktron emails you when the retest +is complete. + +The report download menu offers **Original scan** and **After retest** versions +of the **Full Whitebox Report** and **Executive Report**. Use **After retest** +for the updated results. For older scans, an original report may not be +available if it was not recorded before the retest. + +## If you need another retest + +The dashboard allows only one retest per scan. To verify further fixes, +[start a new scan](/white-box-pentest/quickstart) or email +`hello@hacktron.ai`. A new scan uses the usual +[Whitebox Scan credits](/white-box-pentest/billing). From ae8063a86ee685660b4168a16bcde40e946ee1e7 Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:30:45 +0000 Subject: [PATCH 2/6] style: format existing changelog entry for lint Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- changelog.mdx | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/changelog.mdx b/changelog.mdx index f031c93..dd9dba9 100644 --- a/changelog.mdx +++ b/changelog.mdx @@ -9,27 +9,28 @@ rss: true ## Findings get an identity, a history, and a command palette - **Human-readable finding IDs**: Every finding now has a short, stable ID that appears at the top of the row, in the panel, on the full page, and in the URL. Click the ID to copy it. +**Human-readable finding IDs**: Every finding now has a short, stable ID that appears at the top of the row, in the panel, on the full page, and in the URL. Click the ID to copy it. - **Finding activity timeline**: The finding detail panel gains an Activity tab that shows the full history of a finding: when the engine detected it, which scans sighted it (collapsed into "Detected again in N scans" when consecutive), and every status or severity edit by a team member, with the actor and changed fields on each entry. Switch to the Comments view to see only the thread. +**Finding activity timeline**: The finding detail panel gains an Activity tab that shows the full history of a finding: when the engine detected it, which scans sighted it (collapsed into "Detected again in N scans" when consecutive), and every status or severity edit by a team member, with the actor and changed fields on each entry. Switch to the Comments view to see only the thread. - **Finding actions in the command palette**: With a finding open, the command palette leads with a group of actions for it - change status, change severity, mark or unmark as duplicate, create a ticket, start remediation, copy its ID, copy its link, and open it on the full page. +**Finding actions in the command palette**: With a finding open, the command palette leads with a group of actions for it - change status, change severity, mark or unmark as duplicate, create a ticket, start remediation, copy its ID, copy its link, and open it on the full page. - **New finding filters and multi-ID search**: The findings list gains Source, Reopened, and Date range filters, each saved in the URL. Paste two or more finding IDs into the search box to filter to exactly those findings. +**New finding filters and multi-ID search**: The findings list gains Source, Reopened, and Date range filters, each saved in the URL. Paste two or more finding IDs into the search box to filter to exactly those findings. - **CWE name on hover**: The CWE badge on a finding now shows the full weakness name in a tooltip so you know what you are looking at without leaving the page. +**CWE name on hover**: The CWE badge on a finding now shows the full weakness name in a tooltip so you know what you are looking at without leaving the page. - **Whitebox retest wizard**: Request a retest for a completed scan directly from the scans list or the scan detail page. The retest covers every reported finding except false positives and accepted risk, and the scan detail shows the retest status and results once it is complete. +**Whitebox retest wizard**: Request a retest for a completed scan directly from the scans list or the scan detail page. The retest covers every reported finding except false positives and accepted risk, and the scan detail shows the retest status and results once it is complete. - **Clearer whitebox report coverage**: The Methodology section of a whitebox scan report now shows how many functions each area selected, instead of an arbitrary list of five names. Coverage Detail caps the unselected entry-points table at 50 rows rather than listing every one. +**Clearer whitebox report coverage**: The Methodology section of a whitebox scan report now shows how many functions each area selected, instead of an arbitrary list of five names. Coverage Detail caps the unselected entry-points table at 50 rows rather than listing every one. - **Inline browser-auth instructions in the scan wizard**: The browser-auth audit instructions in the whitebox scan wizard's target step now appear directly on the page with live verification status, instead of opening in a separate modal. +**Inline browser-auth instructions in the scan wizard**: The browser-auth audit instructions in the whitebox scan wizard's target step now appear directly on the page with live verification status, instead of opening in a separate modal. - **PR Review setup vs. active**: The Repositories page now shows a notice when PR Review is toggled on for a repo but no active trial or subscription is backing it, with a direct link to start a trial for owners. +**PR Review setup vs. active**: The Repositories page now shows a notice when PR Review is toggled on for a repo but no active trial or subscription is backing it, with a direct link to start a trial for owners. - **On-prem GitHub.com reachability check**: An on-prem appliance that cannot reach GitHub.com now disables the GitHub.com integration card with a clear reason (DNS, blocked, or TLS) instead of letting you start the setup flow and failing at the code exchange. +**On-prem GitHub.com reachability check**: An on-prem appliance that cannot reach GitHub.com now disables the GitHub.com integration card with a clear reason (DNS, blocked, or TLS) instead of letting you start the setup flow and failing at the code exchange. + +**[See findings →](/api-reference/findings/list-findings)** · **[Start a Whitebox scan →](/white-box-pentest/quickstart)** · **[Set up GitHub →](/platform/repositories/github)** - **[See findings →](/api-reference/findings/list-findings)** · **[Start a Whitebox scan →](/white-box-pentest/quickstart)** · **[Set up GitHub →](/platform/repositories/github)** From 595899c1043a23e2e359a0714361b87e18d1c1c9 Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:42:13 +0000 Subject: [PATCH 3/6] docs: tighten retest copy and recommend reviewing all PRs Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- code-review/overview.mdx | 12 ++--- code-review/troubleshooting.mdx | 11 +++-- white-box-pentest/billing.mdx | 9 +--- white-box-pentest/overview.mdx | 5 +-- white-box-pentest/retests.mdx | 80 +++++++++++++-------------------- 5 files changed, 47 insertions(+), 70 deletions(-) diff --git a/code-review/overview.mdx b/code-review/overview.mdx index 5d0b7b5..e270ce8 100644 --- a/code-review/overview.mdx +++ b/code-review/overview.mdx @@ -9,13 +9,13 @@ Use Code Review for continuous security coverage on day-to-day development. For ## Scan limits -Code Review scans pull requests and merge requests with **up to 500 changed -files**. Larger changes are skipped, not partially scanned. Split them into -separate PRs or MRs with no more than 500 changed files each. +Each PR or MR scan supports **up to 500 changed files**. Hacktron skips larger +PRs and MRs. This limit is separate from your [pooled review allowance](/code-review/spillover-usage) +and does not change with spillover. -This per-scan limit is separate from your organization's -[pooled review allowance](/code-review/spillover-usage). Enabling spillover -does not raise the file limit. +We recommend enabling reviews on all PRs and MRs so smaller changes get reviewed +before they reach a large deployment PR. Keep [all target branches covered](/code-review/setup#choose-covered-branches), +including development branches. ## Quickstart diff --git a/code-review/troubleshooting.mdx b/code-review/troubleshooting.mdx index 823c53c..037bffd 100644 --- a/code-review/troubleshooting.mdx +++ b/code-review/troubleshooting.mdx @@ -46,13 +46,12 @@ you may need to [increase the auto-assignment seat limit](/code-review/people#co ## Pull request or merge request is too large -Each PR or MR scan supports **up to 500 changed files**. If a change exceeds -that limit, Hacktron skips the entire review. It does not scan the first 500 -files, and the skipped review does not count toward your pooled review allowance. +Hacktron skips PRs and MRs with more than **500 changed files**. Skipped reviews +do not use your pooled allowance, and spillover does not raise this limit. -Split the change into separate PRs or MRs with no more than 500 changed files -each. Splitting commits within the same PR or MR does not reduce its file -count. Enabling spillover does not bypass this limit. +Enable reviews on all PRs and MRs, including those targeting development +branches, so changes get reviewed before they reach a large deployment PR. +See [covered branches](/code-review/setup#choose-covered-branches). ## Review limit is reached diff --git a/white-box-pentest/billing.mdx b/white-box-pentest/billing.mdx index d39c6b8..1ae0dd8 100644 --- a/white-box-pentest/billing.mdx +++ b/white-box-pentest/billing.mdx @@ -89,13 +89,8 @@ organization has insufficient Whitebox Scan credits. ## Retests -Each White-box Pentest includes **one free retest**, with no additional -Whitebox Scan credits deducted. You can request it only once per scan, so -finish all the fixes you want verified before submitting. - -For further verification, start a new scan or contact `hello@hacktron.ai`. -A new scan uses the usual Whitebox Scan credits. See -[Retests](/white-box-pentest/retests) for the request steps and results. +Each pentest includes **one free retest**, with no extra Whitebox Scan credits +deducted. See [Retests](/white-box-pentest/retests) for how to request it. ## Refunds and cancellations diff --git a/white-box-pentest/overview.mdx b/white-box-pentest/overview.mdx index 43cda71..eb7c723 100644 --- a/white-box-pentest/overview.mdx +++ b/white-box-pentest/overview.mdx @@ -39,9 +39,8 @@ White-box Pentest is a good fit when you need: ## Verify your fixes -Each scan includes **one free retest**. Once you have fixed the findings you -want verified, [request a retest](/white-box-pentest/retests) from the completed -scan. Hacktron verifies the fixes and makes an updated report available. +Each scan includes **one free retest**. [Request a retest](/white-box-pentest/retests) +after fixing your findings to get an updated report. ## Run status diff --git a/white-box-pentest/retests.mdx b/white-box-pentest/retests.mdx index f5b9eac..a264515 100644 --- a/white-box-pentest/retests.mdx +++ b/white-box-pentest/retests.mdx @@ -3,84 +3,68 @@ title: "Retests" description: "Ask Hacktron to verify your fixes and download an updated pentest report. Each scan includes one free retest." --- -After you fix findings from a White-box Pentest, request a retest from the scan -page. The Hacktron team verifies the fixes and records the result for each -finding. +After fixing your pentest findings, ask the Hacktron team to verify them. - **Each scan includes one free retest.** You can request a retest only once per - scan, so finish all the fixes you want verified before submitting. You cannot - submit another request while the retest is pending or after it is completed. + Each scan includes **one free retest**. Submit once your fixes are ready; you + cannot request another retest for the same scan. ## Before you request a retest -- The scan must be **Completed**, with triage finished and at least one reported finding to retest. -- You need an organization role of **Member** or higher to submit a request. Viewers can read the results. -- Retests are available for White-box Pentests on the hosted platform, not Code Review scans or on-premises deployments. -- Have the branch or commits containing your fixes ready. If the fixes are deployed, have the deployment URLs ready too. - -A retest checks findings from the original scan. To assess new features or -expand the scope, [start a new pentest](/white-box-pentest/quickstart). +Retests are available on the hosted platform for completed White-box Pentests +with triage finished and at least one reported finding. You need a **Member** +role or higher to request one. Viewers can read the results. ## Request a retest - Go to **Whitebox Scans**, open the scan, and click **Request retest**. + In **Whitebox Scans**, open the scan and click **Request retest**. - For each repository, choose the branch containing your fixes. You can also - add commit SHAs under **Commits**, pressing Enter after each one. + Choose the branch containing your fixes for each repository. To add commit + SHAs under **Commits**, press Enter after each one. This is optional. - Add **Deployment URLs** if the fixed version is running, and use - **Summary of fixes** to explain what changed and anything the team needs - to know when verifying. Both fields are optional. + Optionally, add **Deployment URLs** and a **Summary of fixes** to help + the team check your changes. - For a scan of uploaded code, you cannot select a replacement archive here. - Describe the changes in the summary. + For uploaded code, describe the changes in the summary; you cannot + attach a replacement archive. - Check the findings included in the retest. Findings marked **False - positive** or **Accepted risk** are excluded. If a finding should be - excluded, update its status before submitting. + Findings marked **False positive** or **Accepted risk** are excluded. + Check the list and update any statuses before submitting. - Review the repositories, deployment URLs, and summary in **Confirm**, - then click **Request retest**. The scan shows **Retest pending** while - Hacktron verifies the fixes. + Click **Request retest**. The scan shows **Retest pending** while the + team checks your fixes. ### Request limits -- Up to **50 commit SHAs per repository**, each 7 to 40 hexadecimal characters -- Up to **20 deployment URLs**, each starting with `http://` or `https://` -- Up to **10,000 characters** in the summary of fixes +- Up to 50 commit SHAs per repository, each 7 to 40 hexadecimal characters +- Up to 20 deployment URLs, starting with `http://` or `https://` +- Up to 10,000 characters in the summary of fixes ## Read the results -Open **Retest result** on the scan page to check progress. Once verification -is complete, the scan shows **Retested** and each included finding has an -outcome and verification notes: - -| Outcome | Meaning | -| ------------------ | ----------------------------------------------------------------- | -| **Verified fixed** | Hacktron verified the fix. Open findings are marked **Resolved**. | -| **Not fixed** | The issue remains. Read the notes for details. | +When the scan shows **Retested**, open **Retest result** for verification +notes and the outcome of each finding: -If you have email notifications enabled, Hacktron emails you when the retest -is complete. +| Outcome | Meaning | +| ------------------ | ---------------------------------------------- | +| **Verified fixed** | Open findings are marked **Resolved**. | +| **Not fixed** | The issue remains. Read the notes for details. | -The report download menu offers **Original scan** and **After retest** versions -of the **Full Whitebox Report** and **Executive Report**. Use **After retest** -for the updated results. For older scans, an original report may not be -available if it was not recorded before the retest. +You'll also get an email if notifications are enabled. -## If you need another retest +Choose **After retest** when downloading the **Full Whitebox Report** or +**Executive Report**. **Original scan** downloads the earlier version, if +available. -The dashboard allows only one retest per scan. To verify further fixes, -[start a new scan](/white-box-pentest/quickstart) or email -`hello@hacktron.ai`. A new scan uses the usual +For further verification or a wider scope, [start a new scan](/white-box-pentest/quickstart) +or email `hello@hacktron.ai`. New scans use [Whitebox Scan credits](/white-box-pentest/billing). From c1a534898c5d816ab5d4776a6c8fd4c7f98adc25 Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:44:58 +0000 Subject: [PATCH 4/6] docs: link branch coverage guidance to setup section Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- code-review/overview.mdx | 2 +- code-review/troubleshooting.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/code-review/overview.mdx b/code-review/overview.mdx index e270ce8..984a9a0 100644 --- a/code-review/overview.mdx +++ b/code-review/overview.mdx @@ -14,7 +14,7 @@ PRs and MRs. This limit is separate from your [pooled review allowance](/code-re and does not change with spillover. We recommend enabling reviews on all PRs and MRs so smaller changes get reviewed -before they reach a large deployment PR. Keep [all target branches covered](/code-review/setup#choose-covered-branches), +before they reach a large deployment PR. Keep [all target branches covered](/code-review/setup#configure-code-review), including development branches. ## Quickstart diff --git a/code-review/troubleshooting.mdx b/code-review/troubleshooting.mdx index 037bffd..bd8e479 100644 --- a/code-review/troubleshooting.mdx +++ b/code-review/troubleshooting.mdx @@ -51,7 +51,7 @@ do not use your pooled allowance, and spillover does not raise this limit. Enable reviews on all PRs and MRs, including those targeting development branches, so changes get reviewed before they reach a large deployment PR. -See [covered branches](/code-review/setup#choose-covered-branches). +See [covered branches](/code-review/setup#configure-code-review). ## Review limit is reached From 30a0a4bb78d2a056d7dce02335399029d978758b Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:53:12 +0000 Subject: [PATCH 5/6] docs: move scan limits to the end and trim details Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- code-review/overview.mdx | 18 ++++++++---------- code-review/troubleshooting.mdx | 8 +++----- white-box-pentest/retests.mdx | 4 ++-- 3 files changed, 13 insertions(+), 17 deletions(-) diff --git a/code-review/overview.mdx b/code-review/overview.mdx index 984a9a0..db183a0 100644 --- a/code-review/overview.mdx +++ b/code-review/overview.mdx @@ -7,16 +7,6 @@ Code Review reviews pull requests and merge requests in the repositories you ena Use Code Review for continuous security coverage on day-to-day development. For broader, scoped assessments of a repository or application, use [White-box Pentest](/white-box-pentest/overview). -## Scan limits - -Each PR or MR scan supports **up to 500 changed files**. Hacktron skips larger -PRs and MRs. This limit is separate from your [pooled review allowance](/code-review/spillover-usage) -and does not change with spillover. - -We recommend enabling reviews on all PRs and MRs so smaller changes get reviewed -before they reach a large deployment PR. Keep [all target branches covered](/code-review/setup#configure-code-review), -including development branches. - ## Quickstart @@ -81,3 +71,11 @@ including development branches. Manage and provide feedback on findings directly from Slack. + +## Scan limits + +Each PR or MR scan supports **up to 500 changed files**. Hacktron skips larger +PRs and MRs. + +We recommend [enabling reviews on all PRs and MRs](/code-review/setup#configure-code-review) +so smaller changes get reviewed before they reach a large deployment PR. diff --git a/code-review/troubleshooting.mdx b/code-review/troubleshooting.mdx index bd8e479..f3e699b 100644 --- a/code-review/troubleshooting.mdx +++ b/code-review/troubleshooting.mdx @@ -46,12 +46,10 @@ you may need to [increase the auto-assignment seat limit](/code-review/people#co ## Pull request or merge request is too large -Hacktron skips PRs and MRs with more than **500 changed files**. Skipped reviews -do not use your pooled allowance, and spillover does not raise this limit. +Hacktron skips PRs and MRs with more than **500 changed files**. -Enable reviews on all PRs and MRs, including those targeting development -branches, so changes get reviewed before they reach a large deployment PR. -See [covered branches](/code-review/setup#configure-code-review). +[Enable reviews on all PRs and MRs](/code-review/setup#configure-code-review) +so smaller changes get reviewed before they reach a large deployment PR. ## Review limit is reached diff --git a/white-box-pentest/retests.mdx b/white-box-pentest/retests.mdx index a264515..91d2d7b 100644 --- a/white-box-pentest/retests.mdx +++ b/white-box-pentest/retests.mdx @@ -45,8 +45,8 @@ role or higher to request one. Viewers can read the results. ### Request limits -- Up to 50 commit SHAs per repository, each 7 to 40 hexadecimal characters -- Up to 20 deployment URLs, starting with `http://` or `https://` +- Up to 50 commit SHAs per repository +- Up to 20 deployment URLs - Up to 10,000 characters in the summary of fixes ## Read the results From b338fac7aaf6beb3f6cb0c892163161bbcefb17b Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Wed, 21 Oct 2026 10:55:46 +0000 Subject: [PATCH 6/6] docs: simplify retest report guidance Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- white-box-pentest/retests.mdx | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/white-box-pentest/retests.mdx b/white-box-pentest/retests.mdx index 91d2d7b..7fbb7c3 100644 --- a/white-box-pentest/retests.mdx +++ b/white-box-pentest/retests.mdx @@ -61,10 +61,5 @@ notes and the outcome of each finding: You'll also get an email if notifications are enabled. -Choose **After retest** when downloading the **Full Whitebox Report** or -**Executive Report**. **Original scan** downloads the earlier version, if -available. - -For further verification or a wider scope, [start a new scan](/white-box-pentest/quickstart) -or email `hello@hacktron.ai`. New scans use -[Whitebox Scan credits](/white-box-pentest/billing). +After the retest, a new report is added with fix notes showing which findings +were fixed.