Repository navigation
docs: explain pentest retests and scan limits - #89
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: af0e2b66a7
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| 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. |
There was a problem hiding this comment.
Publish the currently enforced 200-file scan limit
For PRs or MRs containing 201–500 changed files, this promises that Code Review will scan them, but the rollout note confirms that production still enforces a 200-file FILE_CHANGE_CAP and skips them. Users following the suggested 500-file split could therefore receive no security review; keep the documentation at 200 until the implementation rollout is complete, or deploy the new limit before publishing these pages.
Useful? React with 👍 / 👎.
|
Browser delta checks passed on local Mintlify at
|
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Summary
Rollout note: Zayne chose 500 as the intended limit. The application code inspected still enforces 200 (
FILE_CHANGE_CAPinapps/iva/src/seat/dev/dev-seat-pr-usage.service.tsin HacktronAI/web). No application code changed; coordinate rollout before publishing the new limit.Targeting
mainwith Zayne's approval because docs has nostagingbranch.Validation:
pnpm lintandpnpm exec mintlify broken-linkspass. Browser-verified the latest copy changes on local Mintlify atb338fac; the unchanged overview placement was checked at30a0a4b. The full guide was checked earlier; product behavior was not tested. Includes a formatter-only fix to the existing changelog entry required by Prettier.Link to Devin session: https://app.devin.ai/sessions/543f63808f494de7995f5b0a894a79f8
Open in Devin Desktop: https://app.devin.ai/desktop/session/543f63808f494de7995f5b0a894a79f8?variant=devin
Requested by: @zeyu2001